Re: http://www.xemacs.org/Releases/Public-21.2/index.html

APA> People will read the page out of context. Therefore, the APA> avoid confusion, I suggest it should be updated from today's APA> point of view in all important places. APA> Stephen, would that be a lot of trouble for you to do? It looks like a substantial amount of work to do accurately. For example, "people with projects" that didn't make it in to 21.4 ought to be polled about status. Also, I suspect that some of the separate project pages may be referenced from outside of that subtree. It would be more natural to update the 2-year gap in the history as it is relevant to new plans when we start planning the next big release. I will get started on revising the pages to make the historical context clear, but I really don't think that's enough. I think the thing to do quickly is to make the reference indirect, except for contexts where it is made clear that this material is of historical interest only. If we can arrange it, a "Warning: this page has has not been updated, and is primarily of historical interest" with an automatic redirect (and pick up any #place if possible) would be best for the indirect reference. Then clean up the other pages gradually, especially the index.html in each directory. Ie, either remove the reference or point out that it's historical. The material really is dated, so it's not really appropriate to refer to it in most contexts. I'll review and revise all the index.content's over the next week or so. Also, I'll put an indirect HTML page in for Release-21.2/index.html. Adrian, could you look in to the possibility of an automatic redirect for that URL? -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.