HI all, I've updated TCW20 (How to Edit the Guidelines) and I'm beginning work on TCW22 (Building a TEI Release). These instructions, along with a lot of our automated processes, assume that the release will be pushed up to SourceForge (therefore requiring that the release technician have shell access to the SF repo). To me this really makes no sense any more; I think we should make this release the point at which we move our products over to both GitHub (for releases from each individual repository) and tei-c.org (for a catalogue of all releases, past and present, in downloadable format). All in favour say aye, all against say why, please. Since we haven't yet established a procedure for doing a release under the new conditions, I don't propose to make it up and describe it ahead of time. I suggest we go through the process, led this time by those with the most familiarity with our past and present systems rather than by a novice release technician, and then construct the documentation after the event, when we know what we ended up doing and what worked. Again, anyone think this is wrong? For the moment, then, what I propose to do with TCW22 is to comment out any references to SF, update any references to svn to refer to git, and leave the document in an incomplete state which retains only the bits that still make sense. Cheers, Martin