According to Lachlan Andrew: > On Tue, 4 Nov 2003 08:42, Neal Richter wrote: > > How about monday the 10th for 3.2.0b5? ... > Sounds good. What needs to be done to make it happen? Gilles > mentioned that Geoff has some scripts to prepare for a release. > Also, someone needs write access to www.htdig.org.
Geoff has some scripts and a checklist. I think it's important to hit all the points on the checklist, but I don't recall what they all are. I know a big part of the release process was sync'ing the docs - i.e. getting the stuff in htdoc in the release in sync with what's in the maindocs cvs, from which the web site is derived. As this is still a beta release, we probably want to keep maindocs as the 3.1.6 stable docs, and put the 3.2.0b5 docs under dev/htdig-3.2 as before, so it's the stuff in that subdirectory that needs to be updated. The syncing also involves copying some stuff from maindocs back into the htdoc directory of the distribution (like the FAQ) and updating some things in both (version specific stuff in FAQ.html, RELEASE.html, where.html, and so on). One tricky bit is the use of style sheets is not consistent between htdoc and maindocs, but that may need to change anyway. I had noticed that the FAQ.html was updated recently in 3.2's htdoc directory, but I've since added another entry in maindocs/FAQ.html. Also, there are fixes in htdig3/htdoc/FAQ.html that aren't in maindocs, so there's probably a need to move some updates in both directions for that file. A diff should help sort things out. One of the things added to htdig3/htdoc/FAQ.html was links to some new, 3.2-specific attributes. If maindocs remains 3.1.6-specific, then the corresponding links in the maindocs FAQ would need to point to dev/htdig-3.2/attrs.html. As far as write access is concerned, my impression was that anyone who has CVS access to the source tree also has write access to the maindocs tree, from which the web docs are maintained. Apart from that, there's also access to /home/groups/h/ht/htdig/htdocs/files from shell.sf.net, to update the http://www.htdig.org/files/ section, which is not maintained through CVS. I think all developers in the htdig group have access to that. There's also the matter of how you post a new release onto the SF download servers, which I've never done, but I think it's supposed to be straightforward. Geoff, if you're still lurking quietly on these lists, this would really, really be a good time to pop out of lurk mode and speak up. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
