good morning again,
first of all, thanks to Guenter and everyone who got the cvsrepository at sourceforge off the ground and running -- yes, Guenter, i really do think that cvs is the "right" way ;-)
now, back to being a bother (sorry): is there a policy regarding the use of symbolic tags in the sourceforge cvs repository? are we planning on using tags to identify releases of external bundles, as well as individual externals? [i ask because now that i've actually managed to import, update, and commit, i feel the irresistible urge to tag (pure habit, but it can be useful)...]
if no policy regarding symbolic tags yet exists, might i suggest the following?
vXX_YY : individual external versioning release_XX_YY : for external "bundles"
alternately, i suppose we could reserve tags like
"EXTERNALNAME_XX_YY"
for individual externals, where "EXTERNALNAME" is the name of the top-level external directory...
marmosets, Bryan
On Thu, 5 Sep 2002, Bryan Jurish wrote:
good morning again,
first of all, thanks to Guenter and everyone who got the cvsrepository at sourceforge off the ground and running -- yes, Guenter, i really do think that cvs is the "right" way ;-)
now, back to being a bother (sorry): is there a policy regarding the use of symbolic tags in the sourceforge cvs repository? are we planning on using tags to identify releases of external bundles, as well as individual externals? [i ask because now that i've actually managed to import, update, and commit, i feel the irresistible urge to tag (pure habit, but it can be useful)...]
if no policy regarding symbolic tags yet exists, might i suggest the following?
vXX_YY : individual external versioning release_XX_YY : for external "bundles"
alternately, i suppose we could reserve tags like
"EXTERNALNAME_XX_YY"
for individual externals, where "EXTERNALNAME" is the name of the top-level external directory...
marmosets, Bryan
I really want to encourage everyone to make suggestions. And I think we have to agree on some tagging philosophy sooner or later.
Do you have a special case for what you want to tag at the moment ? I think that it might be confusing tagging individual externals. For the moment we should probably tag whole directories only, no matter if they are "a bundle" or a single external. The important thing is that when retrieving a tagged version you get everything, working build system and source code that fit together.
This is grounded on my view of tagging as being a way to make some sort of working release of a (sub)-project.
Do we need the vXX_YY and EXTERNALNAME_XX_YY ?
Greetings,
Guenter
Hi Guenter, hi list,
On 9 September 2002 at 13:14:54, guenter geiger wrote:
On Thu, 5 Sep 2002, Bryan Jurish wrote:
[snip]
if no policy regarding symbolic tags yet exists, might i suggest the following?
vXX_YY : individual external versioning release_XX_YY : for external "bundles"
alternately, i suppose we could reserve tags like
"EXTERNALNAME_XX_YY"
for individual externals, where "EXTERNALNAME" is the name of the top-level external directory...
marmosets, Bryan
I really want to encourage everyone to make suggestions. And I think we have to agree on some tagging philosophy sooner or later.
Do you have a special case for what you want to tag at the moment ?
Just a single-package case. I'm in the habit of tagging my own individual "releases" so that they can be easily recovered if things go wrong later.
I think that it might be confusing tagging individual externals.
In the case of multi-external subdirectories (like ggee and ext13), I agree. I've only written 2 externals, though (and only 1 is already in CVS), so when I say 'individual externals', I suppose I mean 'independent external(s) distributions or packages', which in my case are identical with 'individual externals'...
For the moment we should probably tag whole directories only, no matter if they are "a bundle" or a single external. The important thing is that when retrieving a tagged version you get everything, working build system and source code that fit together. This is grounded on my view of tagging as being a way to make some sort of working release of a (sub)-project.
Yes.
Do we need the vXX_YY and EXTERNALNAME_XX_YY ?
My thought was that these were alternative ways of realizing the same flavor of tag -- package-local tags for independent external(s)-distributions. I suppose it would be better to phrase this:
PACKAGENAME_XX_YY
Really, we'd just need to reserve 'PACKAGENAME_' prefixes for all subdirectories '${CVSROOT}/pure-data/PACKAGENAME' and '${CVSROOT}/pure-data/externals/PACKAGENAME'. I think that reserving tags of this type is important so that the maintainers of the individual subdirectories can use 'cvs tag -F' with impunity -- i.e. for patching existing releases.
Tags for "bundled releases" (distributions consisting of multiple "packages", i.e. comrpising multiple subdirectories of 'externals/') are harder to conventionalize, since they may require coordination on the part of various package maintainers... since I'm not yet involved with anything of this nature, I can only speculate as to what would be required, but a reserved tag-prefix doesn't seem sufficient here....
marmosets, Bryan
-
Bryan Jurish -
guenter geiger