It is my pleasure to announce that I have been appointed as the release manager for the upcoming releases. For 2.5.2, I would like to release a candidate on February 14, and the final version on February 21. As Guido already mentioned, this will be a bug fix release only; no new features allowed. Kind regards, Martin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin v. Löwis wrote: | It is my pleasure to announce that I have been appointed as the release | manager for the upcoming releases. For 2.5.2, I would like to release | a candidate on February 14, and the final version on February 21. As | Guido already mentioned, this will be a bug fix release only; no new | features allowed. As current bsddb module maintainer, I was wondering if 2.5.2 will support BerkeleyDB 4.6 :-?. - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ ~ _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBR6B+jZlgi5GaxT1NAQIX+QQAl7PFJtZb64kiTpewupJppos5mAXFKB29 lrud1t6AkgFOgvE9M45ISCwTDzbSa4qLOiDX/v5F9RltcH+RK5Tlu3eTR8Djmn6q PSzjo92LZx7wudq2WaBL2+PIE/IhAOO9gKHtwNtB3iXQGTl8NKIIJUbkDUclvPPv bH97ECQvb7U= =yV47 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin v. Löwis wrote: |> As current bsddb module maintainer, I was wondering if 2.5.2 will |> support BerkeleyDB 4.6 :-?. | | Maybe I'm misunderstanding the question - whom are asking? | If me - Python 2.5.2 will essentially do what the maintenance branch | does currently. I beg your pardon. My role is recent (a week) and I'm still learning my way thru procedures and conventions :-). Current bsddb module in 2.5.1 supports up to BerkeleyDB 4.5. There is support for 4.6 in trunk (future 2.6, I guess) and I'm working in a private branch at the moment, since I have no commit access to python repository. That private version is intented to be merged into python 2.6 by Greg, when time comes. My guess is that 2.5 branch is still open to more patches than pure security/stability patches, so "backporting" BerkeleyDB 4.6 support seems reasonable (to me). If I'm wrong, please educate me :-). This backport would include also stability patches. For example, I just solved a memory leak. Greg, any opinion?. Beware, new kid in the block! :). - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ ~ _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBR6GX/Zlgi5GaxT1NAQLZfQP/Zl95IiH9wyIaVA2K2ulxnQG6Su7OKASM p4Ej3c2/1JHxprabXixDdn2i8fPZJ+02qMbJIxmWhupvW5TpHsoH4Rrs0QV/+SpD LFvvIgVruJCaVgZUFEoqOoRA07OwxRwg6tgPLPwsVcKZISTBRGRBiARply83vaDz hjjFA5abVPU= =Jti3 -----END PGP SIGNATURE-----
On 1/31/08, Christian Heimes <lists@cheimes.de> wrote:
Actually in all past releaseXX-maint branches I have merged in support for compiling against a new version of BerkeleyDB. Its not a feature, its just something you have to do to support compiling against a new library version. Why is this ok? * There are no API changes on the python module side. * Binary releases of python for windows continue to be compiled against the same BerkeleyDB version that was used in the 2.5.0 release. the combo of those two things keeps it sane to do this. As Martin pointed out, I already merged that trivial change in to release25-maint a while back. That said, BerkeleyDB 4.6.x has proven to be a bit of an unstable release from Oracle so I'm considering modifying setup.py to disable linking against that version by default. I'll be reviewing buildbot results this weekend. As already mentioned by Neal i've disabled 4.6 support in trunk to watch the buildbots. I'll go over the results this weekend to make a decision on whether or not python's setup.py should default to allowing itself to link against 4.6.x or not in hopes of avoiding people filing bugs against us for what is ultimately Oracle's problem. -Greg
On Thu, Jan 31, 2008, Jesus Cea wrote:
Please read PEP6: http://www.python.org/dev/peps/pep-0006/ The gist is that point releases are purely bugfix releases, because adding features lessens code quality and makes it more difficult to track changes. The big push to stick with PEP6 came from the mistake of adding True/False to Python 2.2.1. -- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ "All problems in computer science can be solved by another level of indirection." --Butler Lampson
I think it depends on the nature of the patch. The 2.5 branch already supports BerkeleyDB 4.6 (since r58345), so I'm not sure what else needs to be done.
Being new is not a problem in itself. But do please take the extra work of double- and triple-checking any claims you make. If you want to become the new maintainer of the bsddb module, you need to learn how to check out a branch of Python and how to determine what patches have been applied to it. Regards, Martin
On Jan 31, 2008 1:42 AM, Jesus Cea <jcea@argo.es> wrote:
Note that db 4.6 might be the cause of some crashes on the buildbots: http://www.python.org/dev/buildbot/all/ I asked to have it disabled on one platform (sparc). I haven't checked the results and I'm not sure if Greg has either. Greg checked in a change to setup.py on trunk to disable 4.6 to see if the crashes go away. ~5 buildbots had crashes in bsddb or related code with 4.6 before the change to setup.py. n
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin v. Löwis wrote: | It is my pleasure to announce that I have been appointed as the release | manager for the upcoming releases. For 2.5.2, I would like to release | a candidate on February 14, and the final version on February 21. As | Guido already mentioned, this will be a bug fix release only; no new | features allowed. As current bsddb module maintainer, I was wondering if 2.5.2 will support BerkeleyDB 4.6 :-?. - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ ~ _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBR6B+jZlgi5GaxT1NAQIX+QQAl7PFJtZb64kiTpewupJppos5mAXFKB29 lrud1t6AkgFOgvE9M45ISCwTDzbSa4qLOiDX/v5F9RltcH+RK5Tlu3eTR8Djmn6q PSzjo92LZx7wudq2WaBL2+PIE/IhAOO9gKHtwNtB3iXQGTl8NKIIJUbkDUclvPPv bH97ECQvb7U= =yV47 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin v. Löwis wrote: |> As current bsddb module maintainer, I was wondering if 2.5.2 will |> support BerkeleyDB 4.6 :-?. | | Maybe I'm misunderstanding the question - whom are asking? | If me - Python 2.5.2 will essentially do what the maintenance branch | does currently. I beg your pardon. My role is recent (a week) and I'm still learning my way thru procedures and conventions :-). Current bsddb module in 2.5.1 supports up to BerkeleyDB 4.5. There is support for 4.6 in trunk (future 2.6, I guess) and I'm working in a private branch at the moment, since I have no commit access to python repository. That private version is intented to be merged into python 2.6 by Greg, when time comes. My guess is that 2.5 branch is still open to more patches than pure security/stability patches, so "backporting" BerkeleyDB 4.6 support seems reasonable (to me). If I'm wrong, please educate me :-). This backport would include also stability patches. For example, I just solved a memory leak. Greg, any opinion?. Beware, new kid in the block! :). - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ ~ _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBR6GX/Zlgi5GaxT1NAQLZfQP/Zl95IiH9wyIaVA2K2ulxnQG6Su7OKASM p4Ej3c2/1JHxprabXixDdn2i8fPZJ+02qMbJIxmWhupvW5TpHsoH4Rrs0QV/+SpD LFvvIgVruJCaVgZUFEoqOoRA07OwxRwg6tgPLPwsVcKZISTBRGRBiARply83vaDz hjjFA5abVPU= =Jti3 -----END PGP SIGNATURE-----
On 1/31/08, Christian Heimes <lists@cheimes.de> wrote:
Actually in all past releaseXX-maint branches I have merged in support for compiling against a new version of BerkeleyDB. Its not a feature, its just something you have to do to support compiling against a new library version. Why is this ok? * There are no API changes on the python module side. * Binary releases of python for windows continue to be compiled against the same BerkeleyDB version that was used in the 2.5.0 release. the combo of those two things keeps it sane to do this. As Martin pointed out, I already merged that trivial change in to release25-maint a while back. That said, BerkeleyDB 4.6.x has proven to be a bit of an unstable release from Oracle so I'm considering modifying setup.py to disable linking against that version by default. I'll be reviewing buildbot results this weekend. As already mentioned by Neal i've disabled 4.6 support in trunk to watch the buildbots. I'll go over the results this weekend to make a decision on whether or not python's setup.py should default to allowing itself to link against 4.6.x or not in hopes of avoiding people filing bugs against us for what is ultimately Oracle's problem. -Greg
On Thu, Jan 31, 2008, Jesus Cea wrote:
Please read PEP6: http://www.python.org/dev/peps/pep-0006/ The gist is that point releases are purely bugfix releases, because adding features lessens code quality and makes it more difficult to track changes. The big push to stick with PEP6 came from the mistake of adding True/False to Python 2.2.1. -- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ "All problems in computer science can be solved by another level of indirection." --Butler Lampson
I think it depends on the nature of the patch. The 2.5 branch already supports BerkeleyDB 4.6 (since r58345), so I'm not sure what else needs to be done.
Being new is not a problem in itself. But do please take the extra work of double- and triple-checking any claims you make. If you want to become the new maintainer of the bsddb module, you need to learn how to check out a branch of Python and how to determine what patches have been applied to it. Regards, Martin
On Jan 31, 2008 1:42 AM, Jesus Cea <jcea@argo.es> wrote:
Note that db 4.6 might be the cause of some crashes on the buildbots: http://www.python.org/dev/buildbot/all/ I asked to have it disabled on one platform (sparc). I haven't checked the results and I'm not sure if Greg has either. Greg checked in a change to setup.py on trunk to disable 4.6 to see if the crashes go away. ~5 buildbots had crashes in bsddb or related code with 4.6 before the change to setup.py. n
participants (6)
-
"Martin v. Löwis" -
Aahz -
Christian Heimes -
Gregory P. Smith -
Jesus Cea -
Neal Norwitz