-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 1, 2008, at 10:38 AM, Steve Holden wrote:

Barry Warsaw wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Mar 1, 2008, at 12:36 AM, Steve Holden wrote:

...

If you can document the web stuff you have to do I will formalize it as a procedure for use in future releases.

Hi Steve,

In this case, there was a lot more work to do because 2.6 wasn't tied in at all. Add to the fact that I didn't have any experience with the website infrastructure made things a bit more difficult the first time out. I still don't quite have the 2.6 links working correctly in my local fs. So the biggest problem is really: what steps do you take when you need to expose a new major release on the website?

I guess the thing to do is to look at your diffs once you have committed the changes - I presume this'll all be dropped in as a single revision?

That would be great Steve, thanks! r11294. I'm going to build Python 3.0 now. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR8mEw3EjvBPtnXfVAQKm9gP+PdoDvqTmA4kuqVrNmQJdHSsQDVcB7/sV BRxeYH0S1TNo05NCzv6qyJ6nxe2CVI6he+chhoCbtCRqp6c5LQOXtaSHUqoSNzP9 FSw9YnQ3DHmFRX3BfNyZ7d9FS2Fs5irsLuAc+WUFNR0AWsvbwXR6qlT0qNQGP666 V46DiUdNhUA= =ybmk -----END PGP SIGNATURE-----