-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Nov 18, 2008, at 5:03 AM, Facundo Batista wrote: > 2008/11/17 Barry Warsaw <barry at python.org>: > >> Martin suggests, and I agree, that we should release Python 3.0 >> final and >> 2.6.1 at the same time. Makes sense to me. That would mean that >> Python >> 2.6.1 should be ready on 03-Dec (well, if Python 3.0 is ready then!). > > 2.6.1 only two months after 2.6? Why so quickly? Actually, I've wanted to do timed releases, though I think monthly is unrealistic. Maybe every two months is about the right time frame. Timed releases are nice because everybody then knows when a patch is due, from developers to downstream consumers. > Anyway, I don't see any added value in the synchronization, so taking > in consideration all the effort you're putting in these releases, I > would just want to minimize your workload... which is easier to you? > doing both at the same time or not? We're getting releases down to a science now! :) Actually the most painful part is updating the web site, so I plan adding some automation around that process too. OTOH, this is the first point release I'll be doing with the new script, so it'll be interesting to debug that process. As for synchronization, I think it's a good habit to get into, if my plan to do timed releases works out. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSSLShXEjvBPtnXfVAQL90QP/UfWRXr0esTim+DtQJs9Fd/+Lj9PpuBV6 UCB7pAwl8uf7qIAwjDkCsdg3VD/wxzmzuwDAB8T19PF5dNxsrKWdBEzhymVpLU8T cch0Vlaevm6Co/kDp8VhyoKlPs7LDhGkC2G04qDSOETo8Ci84rBOlWd7n1KvUrYZ 01Pn6eZHdqA= =k9FS -----END PGP SIGNATURE-----
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4