Gregory (Grisha) Trubetskoy wrote:
On Tue, 7 Jun 2005, Nicolas Lehuen wrote:
Grisha, can you tell us what is the process to release a new version,
including the update of the web site ?
Updating the site is trivial, I can do it, that's the last thing to
worry about. Releasing a new version is a bit more complicated.
Maybe we could have a svn branch for the website? Then it's even more
trivial for you to update.
The instructions for making the actual tgz file are at the bottom of
Doc/Makefile file. I have no idea why I decided to stick them there,
perhaps it's better to create a separate file called
Doc/release-instructions.txt or something.
I can do this. Doc/release-instructions.txt seems like a good choice.
The instructions were written with CVS in mind so we'll need to figure
out the SVN counterparts of the required commands.
I took a quick look and there is nothing tricky there. Biggest
difference is svn copy is used instead of cvs tag. I'll make the changes
when I split the release instructions into a new file.
You'll definitely need to be on a unix machine of some sort that has
TeTeX installed to produce the documentation, it's actually pretty easy.
I've had good success in generating the docs. The only trick is editing
the Makefile to point to the python src directory.
This being a somewhat major release, I think we should perhaps tag it
3.2.0-rc1 (to be followed by rc2, etc).
Agreed.
Once the tgz file is ready we will need to collect votes on the list to
make sure it actually works. Once it's been tested anough by the folks
on the list (we need 4 or more I think) enough votes are collected, it
can be released on the apache site and formally announced.
Just so I understand, is this voting on mod_python or python-dev list?
Regards,
Jim
