As I've already said in another thread, I plan for 3.2.1 r2 as soon as http://bugs.python.org/issue12084 is fixed. This is hopefully this weekend, but may be next. Final is, as always, one week later.
Georg
Le jeudi 19 mai 2011 à 20:33 +0200, Georg Brandl a écrit :
As I've already said in another thread, I plan for 3.2.1 r2 as soon as http://bugs.python.org/issue12084 is fixed. This is hopefully this weekend, but may be next. Final is, as always, one week later.
If I would like to touch Python 3.2, but the change doesn't need to be included into Python 3.2.1, can I push directly into the "3.2" branch?
Georg: do you work directly on the 3.2 branch, or do you have another repository?
A problem is that Misc/NEWS refers to Python 3.2.1 and not yet to 3.2.2.
Victor
On 05/22/11 16:11, Victor Stinner wrote:
Le jeudi 19 mai 2011 à 20:33 +0200, Georg Brandl a écrit :
As I've already said in another thread, I plan for 3.2.1 r2 as soon as http://bugs.python.org/issue12084 is fixed. This is hopefully this weekend, but may be next. Final is, as always, one week later.
If I would like to touch Python 3.2, but the change doesn't need to be included into Python 3.2.1, can I push directly into the "3.2" branch?
I will split the 3.2.1rc2 release branch from the main branch next week, so commits done to 3.2 now go into 3.2.1.
But it seems your change isn't fit for any 3.2 anyway.
Georg: do you work directly on the 3.2 branch, or do you have another repository?
Once rc2 is split, I'll work in the same release clone I used for rc1.
A problem is that Misc/NEWS refers to Python 3.2.1 and not yet to 3.2.2.
That's just fine as it is.
Georg
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 19/05/11 20:33, Georg Brandl wrote:
As I've already said in another thread, I plan for 3.2.1 r2 as soon as http://bugs.python.org/issue12084 is fixed. This is hopefully this weekend, but may be next. Final is, as always, one week later.
Would you comment about the push policy to 3.2 branch?.
Are you doing the release work in a separate clone?. Can we push to 3.2 with no restrictions?. That would be a very nice side effect of mercurial migration.
Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ 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.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBTdmzvplgi5GaxT1NAQInFQP8CCrC34ShasTq1OeyCnlZynOib4mGmpxK 27/wDnasq4amVmJNoXaxWmuiRHVzfXPtcph/lYb1kySpKBUaWotmznJBGPdTi4MO 52Za2+qhLWT3L2Dbm3g8Rg+jTinqzSiERMy998jSvK8Wwa1VIpiBgL08EKOiS4Qj 5CYYtT7owjc= =bnvI -----END PGP SIGNATURE-----
On 23.05.2011 03:09, Jesus Cea wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 19/05/11 20:33, Georg Brandl wrote:
As I've already said in another thread, I plan for 3.2.1 r2 as soon as http://bugs.python.org/issue12084 is fixed. This is hopefully this weekend, but may be next. Final is, as always, one week later.
Would you comment about the push policy to 3.2 branch?.
Are you doing the release work in a separate clone?. Can we push to 3.2 with no restrictions?. That would be a very nice side effect of mercurial migration.
I've already said that: yes, there is no restriction.
I will take all changes into rc2. It will take the role of rc1, hopefully without blockers this time.
Georg
On Thu, May 19, 2011 at 13:33, Georg Brandl <g.brandl@gmx.net> wrote:
As I've already said in another thread, I plan for 3.2.1 r2 as soon as http://bugs.python.org/issue12084 is fixed. This is hopefully this weekend, but may be next. Final is, as always, one week later.
Georg
Sorry for taking so long to finish it, but I now have a patch completed for #12084. It's Windows specific so I don't imagine there are a lot of interested reviewers, but at least a quick look to make sure I'm not doing anything too crazy would be greatly appreciated so Georg and the crew and get on with the release process.
The full test suite passes, but keep in mind that symlinks on Windows require administrator privileges. My build slave is the only one which runs as admin and it's not currently running very well. Now that I fixed this bug, I'll get the bot back up and running.
On 06/03/11 01:28, Brian Curtin wrote:
On Thu, May 19, 2011 at 13:33, Georg Brandl <g.brandl@gmx.net <mailto:g.brandl@gmx.net>> wrote:
As I've already said in another thread, I plan for 3.2.1 r2 as soon as http://bugs.python.org/issue12084 is fixed. This is hopefully this weekend, but may be next. Final is, as always, one week later. GeorgSorry for taking so long to finish it, but I now have a patch completed for #12084. It's Windows specific so I don't imagine there are a lot of interested reviewers, but at least a quick look to make sure I'm not doing anything too crazy would be greatly appreciated so Georg and the crew and get on with the release process.
The full test suite passes, but keep in mind that symlinks on Windows require administrator privileges. My build slave is the only one which runs as admin and it's not currently running very well. Now that I fixed this bug, I'll get the bot back up and running.
Good timing... I'm just leaving for vacation :) I am not certain, but if all goes as planned I might still have some time between this and next weekend to get out a rc2, and reserve the weekend of the 18th/19th for the final. I'll put that in the release calendar for now.
cheers, Georg
participants (4)
-
Brian Curtin -
Georg Brandl -
Jesus Cea -
Victor Stinner