I've volunteered to be the Release Manager for Python 3.4. The FLUFL has already given it his Sloppy Wet Kiss Of Approval, and we talked to Georg and he was for it too. There's no formal process for selecting the RM, so I may already be stuck with the job, but I thought it best to pipe up on python-dev in case someone had a better idea. But look! I'm already practicing: NO YOU CAN'T CHECK THAT IN. How's that? Needs work? I look forward to seeing how the sausage is made, /larry/
On Nov 22, 2011, at 7:50 PM, Larry Hastings wrote:
I've volunteered to be the Release Manager for Python 3.4.
Awesome. Thanks for stepping up.
The FLUFL has already given it his Sloppy Wet Kiss Of Approval,
Ewwww!
and we talked to Georg and he was for it too. There's no formal process for selecting the RM, so I may already be stuck with the job, but I thought it best to pipe up on python-dev in case someone had a better idea.
But look! I'm already practicing: NO YOU CAN'T CHECK THAT IN. How's that? Needs work?
You could try a more positive leadership style: THAT LOOKS GREAT, I'M SURE THE RM FOR PYTHON 3.5 WILL LOVE IT ;-) Raymond
On Tue, Nov 22, 2011 at 08:27:24PM -0800, Raymond Hettinger wrote:
On Nov 22, 2011, at 7:50 PM, Larry Hastings wrote:
But look! I'm already practicing: NO YOU CAN'T CHECK THAT IN. How's that? Needs work?
You could try a more positive leadership style: THAT LOOKS GREAT, I'M SURE THE RM FOR PYTHON 3.5 WILL LOVE IT ;-)
Wow! My release engineering team needs to take classes from you guys! -Toshio
On Tue, 22 Nov 2011 20:27:24 -0800 Raymond Hettinger <raymond.hettinger@gmail.com> wrote:
But look! I'm already practicing: NO YOU CAN'T CHECK THAT IN. How's that? Needs work?
You could try a more positive leadership style: THAT LOOKS GREAT, I'M SURE THE RM FOR PYTHON 3.5 WILL LOVE IT ;-)
How about: PHP 5.5 IS NOW OPEN FOR COMMIT ?
Antoine Pitrou writes:
On Tue, 22 Nov 2011 20:27:24 -0800 Raymond Hettinger <raymond.hettinger@gmail.com> wrote:
But look! I'm already practicing: NO YOU CAN'T CHECK THAT IN. How's that? Needs work?
You could try a more positive leadership style: THAT LOOKS GREAT, I'M SURE THE RM FOR PYTHON 3.5 WILL LOVE IT ;-)
How about: PHP 5.5 IS NOW OPEN FOR COMMIT ?
I thought Larry's version was somewhat more encouraging.
On Wed, Nov 23, 2011 at 11:50 AM, Larry Hastings <larry@hastings.org> wrote:
I've volunteered to be the Release Manager for Python 3.4. The FLUFL has
That's cool. But just my thought, wouldn't it be better for someone who regularly commits, fixes bugs and feature requests be better for a RM role? Once a developer gets bored with those and wants more, could take up RM role. Is there anything wrong with this kind of thinking? Thanks, Senthil
On Wed, Nov 23, 2011 at 2:50 PM, Senthil Kumaran <senthil@uthcode.com> wrote:
On Wed, Nov 23, 2011 at 11:50 AM, Larry Hastings <larry@hastings.org> wrote:
I've volunteered to be the Release Manager for Python 3.4. The FLUFL has
That's cool. But just my thought, wouldn't it be better for someone who regularly commits, fixes bugs and feature requests be better for a RM role? Once a developer gets bored with those and wants more, could take up RM role. Is there anything wrong with this kind of thinking?
The main (thoroughly informal) criteria are having commit privileges, having shown some evidence of "getting it" when it comes to the release process and then actually putting your hand up to volunteer. Most people who pass the second criterion seem to demonstrate this odd reluctance to meet the third criterion ;) There's probably a fourth criterion of the other devs not going "Arrg, no, not *them*!", but, to my knowledge, that's never actually come up... I'm sure Larry will now be paying close attention as Georg shepherds 3.3 towards release next year, so it sounds like a perfectly reasonable idea to me. +1 Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Wed, Nov 23, 2011 at 6:50 AM, Senthil Kumaran <senthil@uthcode.com> wrote:
That's cool. But just my thought, wouldn't it be better for someone who regularly commits, fixes bugs and feature requests be better for a RM role? Once a developer gets bored with those and wants more, could take up RM role. Is there anything wrong with this kind of thinking?
There is something to be said for letting those people continue to regularly commit and fix bugs rather than saddling them with the RM role. :) Schiavo Simon
On Nov 22, 2011, at 07:50 PM, Larry Hastings wrote:
I've volunteered to be the Release Manager for Python 3.4. The FLUFL has already given it his Sloppy Wet Kiss Of Approval,
I think you mistook that for my slackjaw droolings when you repeatedly ignored my warnings to run as far from it as possible. But you're persistent, I'll give you that. Looks like that persistence will be punis^H^H^H^H^Hrewarded with your first RMship! Congratulations (?).
and we talked to Georg and he was for it too. There's no formal process for selecting the RM, so I may already be stuck with the job, but I thought it best to pipe up on python-dev in case someone had a better idea.
But look! I'm already practicing: NO YOU CAN'T CHECK THAT IN. How's that? Needs work?
I look forward to seeing how the sausage is made,
Undoubtedly it will make you a vegan, but hopefully not a Go programmer! :) Seriously though, I think it's great for you to work with Georg through the 3.3 process, so you can take over for 3.4. And I also think it's great that someone new wants to do it. I kid, but the mechanics of releasing really isn't very difficult these days as we've continually automated the boring parts. The fun part is really making the decisions about what is a showstopper, what changes can go in at the last minute, etc. Like the president of the USA, I just hope your hair is already gray! -Barry
participants (9)
-
Antoine Pitrou -
Barry Warsaw -
Larry Hastings -
Nick Coghlan -
Raymond Hettinger -
Senthil Kumaran -
Simon Cross -
Stephen J. Turnbull -
Toshio Kuratomi