Re: branching in packages?
Never insisted on creating separate branches for pre- release and
stable packages in package cvs. All that asked was *procedures* to
obtain / retrieve latest stable or latest pre- release package working
directory from cvs. And markup in cvs for use in such procedures -
whatever you choose.
Currently cvs certainly contains package version tags. But these tags
do not specify whether the version is stable, and thus useless for the
task described above.
If you would like to maintain separate branches of packages of
special
interest to you in our CVS, that can probably be arranged (Norbert,
what say you?), but since ISTR you have code that can't be released to
the public, that's probably more trouble than it's worth. :-(
Wherever these branches are kept, one still has to sync / merge them
with upstream sources, and, for some branches, take stable upstream
versions for the sync. Which means the task above.
As for keeping my branches in your CVS - thanks for invitation; all my
code certainly can be released to the public. OTOH, can have my own
CVS, and certainly there is no reason to bother you or other CVS
maintainers with requests to keep my branches. This is why never
asked for that.