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 May we consider switching the semantics of the tags so that "release-21.2" is the latest beta known to compile somewhere, and "r21-2-latest" is the current, not necessarily coherent, state of the CVS head? Or maybe retire "release-21.2" and use "r21-2-latest-beta" (or one of the two obvious abbreviations, I favor "r21-2-beta" for brevity and clarity) for the most recent consistent sources and "r21-2-head", "r21-2-current" (I don't like it, too similar to "latest"), or "r21-2-bleeding-edge" for the possibly inconsistent head of the branch? Sorry, I should have thought about this before when you posted your "Engineering Changes" proposal. But it just hit me smack in the face when you juxtaposed a tag named "release" with "may not even compile"! -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."