On 1/31/07, Randy McMurchy <[EMAIL PROTECTED]> wrote: > Bruce Dubbs wrote these words on 01/31/07 20:27 CST: > > Randy McMurchy wrote: > >> Why not update a tag? > > > > You can. You asked for opinions. > > And I appreciate your comments. And I value them. But in our world > of a book that is constantly being updated, SVN *tags* would be > worthless. There is never a need to create snapshot of trunk, unless > it is being used for backup purposes. > > In a typical package type repo, where versions are constantly changing, > tags are effective. You can update the configure.ac file, tag it and > move on in trunk. In a typical package environment, > *you would never need to go back to a previous version*, the version > is constantly being updated. > > But in our book environment, SVN trunk is everything, and any deviation > from trunk (the annual or semi-annual release) is so infrequent that > it doesn't make sense to me to adhere to this stigma of not updating > a tag. > > My belief (and I'm quite strong on this one) is that we should use > SVN in our best interests, which means for us (at least in my opinion) > that tags are a stagnant entity, but branches are meant to be used > for merges from trunk. > > Is there any real reason to treat our book SVN any different than > how I'm proposing? Is there some reason that we shouldn't make *one* > commit to a tag, which then identifies it as a unique and unchanging > version of our book? > > To summarize: > > Tags contain data that won't be changed once the tag is finished. > Branches contain data that is expected to be changed. Once a branch > is no longer being updated, create a tag, remove the branch and drive > on with trunk. > > At least that's how I look at it. I would love to gather more input > from others about my thoughts.
As I've always understood release management from other software projects, the tag is meant to be fixed. As in, I can always pull the firefox source with the CVS tag FIREFOX_1_0_5_1_RELEASE and know I'm getting the same thing that's in the tarball. I would like to see a 6.2 branch created and have the tags generated from that branch. But, you're the boss. As long as there's a place to check in 6.2 specific changes. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
