Re: How does tag r21-5-latest-beta work?

|--==> "APA" == Adrian Aichner <adrian(a)xemacs.org&gt; writes: SY> By yours truly. :-) Usually after my 6th or 7th coffee for the day I SY> might say "lets release a beta, just for kicks..."[1]. After I've APA> Oh, in that case you need to put your coffee statistics up under APA> http://www.xemacs.org/coffee/ so that the beta community can track the APA> tagging progress. Sure, just as soon as I patch coffee.el to automatically update the stats for me. :-) SY> Is that nifty or what? :-) APA> Yep. APA> So r21-5-latest-beta is basically an alias for the latest tagged beta APA> release, right? I suppose that you could put it that way, yes. SY> Latest beta release sources. In other words, the contents of SY> 'xemacs-21.5.10.tar.gz' on ftp.xemacs.org is more or less identical to SY> what the current r21-5-latest-beta tag points to in CVS. APA> Why "more or less"? What's the variance between the two? Is it other APA> people commiting between your tagging operations? No, it's nothing like that. The differences are that the tarball doesn't have any 'CVS' directories or '.cvsignore' files[1], and there are no '.info' files in CVS whereas they exist in the tarball. To put your mind at rest, if someone was to commit between my tagging operations I wouldn't be affected (unless I 'cvs up' in between the 2 tags). CVS tags the repository from the versions of the files in my workspace, it doesn't matter if newer versions of the files exist in the repository. APA> Would be nice to have explanations of our tagging name conventions on APA> the website, perhaps reachable via http://www.xemacs.org/Develop/ http://www.xemacs.org/Develop/cvsaccess.html#tags Footnotes: [1] I also clean out any .orig and .rej files that may be in my workspace. -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|