Re: XEmacs 21.2.24 is released.

mb> You can be at the bleeding edge mb> cvs checkout -r release-21.2 mb> You can get the latest released beta mb> ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.2/xemacs-21.2.24.* mb> cvs checkout -r r21-2-24 mb> cvs checkout -r r21-2-latest ST> May we consider switching the semantics of the tags so that "release-21.2" ST> is the latest beta known to compile somewhere, and "r21-2-latest" is ST> the current, not necessarily coherent, state of the CVS head? No can do. release-21-2 names a BRANCH, while r-21-2-latest names the state at a particular time, namely a beta release. But I see that this is indeed confusing. I would like to take the lead of gcc and call it r-21-2-latest-snapshot, but r-21-2-latest-beta suits our history better. I'll change the name next beta. It would be better to use the work `branch' in the name release-21-2, to make it clearer what is a branch and what isn't. This distinction is hard to understand until you study it for a while. ST> Or maybe retire "release-21.2" and use "r21-2-latest-beta" (or one of ST> the two obvious abbreviations, I favor "r21-2-beta" for brevity and ST> clarity) for the most recent consistent sources and "r21-2-head", ST> "r21-2-current" (I don't like it, too similar to "latest"), or ST> "r21-2-bleeding-edge" for the possibly inconsistent head of the ST> branch? Again, the problem is that the head of the branch itself doesn't have a name, but the branch as a whole does. And then there's the trunk - it doesn't even have a name :( ST> Sorry, I should have thought about this before when you posted your ST> "Engineering Changes" proposal. But it just hit me smack in the face ST> when you juxtaposed a tag named "release" with "may not even compile"! Hmmmmm... dev-21-2-branch branch-21-2 dev-21-2 (can't start with a number) Martin