-----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? - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR8lkF3EjvBPtnXfVAQLjtQP/cyIu6i/3hL7RMyJjwi5UWaVelq+6+DjX c8P6aLT0Gq2jIIacwt2P5lWYGx5D2nahoLCkLoA4M3avHM6UiTaIW45nFrnffItx F/ib/UY/j+gsudlg5GsZQrBTzvrso6BFDuIr9VISuzf3e6QRr7sAhUfXzgIETXjj DPT3y474bDs= =Kxv7 -----END PGP SIGNATURE----- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com