sb> Jan Vroonhof <vroonhof(a)math.ethz.ch&gt; writes in xemacs-beta(a)xemacs.org: sb> ... sb> It should not be ditched. It is not subject to any of the whims and sb> badness that Usenet is subject to. It is possible to subscribe sb> xemacs(a)xemacs.org to it the same way xemacs-beta(a)xemacs.org is sb> subscribed to it. I've resisted doing this for various reasons, but sb> it is perhaps the best thing to do now. We should *definitely* route it to comp.emacs.xemacs, though. I just plain don't understand why people think that posting announcements to xemacs-announce is sufficient. We should announce everything we release---binary kits, minor releases---except for betas on comp.emacs.xemacs. We should also do comp.emacs and gnu.announce. This is extremely low-effort. We *need* more publicity, at least with especially after the long wait following 20.4 and the 21.0.67 announcement disaster. I'm also still all for formalizing stable and release branches the way FreeBSD does, and release stable every three or four months, whatever's on it. sb> I am leery of separating CVS components and we do not have a CVS sb> server running on www.xemacs.org. I don't understand why. Could you explain? sb> Maybe the thing to do is move the webpages to cvs.xemacs.org and sb> automatically mirror a checked out copy to the webserver. Anyone sb> interested in putting the scripts together to do this? I do know how to set up CVS such that it automatically checks out every commit right away. srfi.schemers.org is managed this way. If I can help, I'll volunteer. This simplifies updating the web site by an order of magnitude, and is likely to attract more volunteers as well. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla