On Sat, Feb 22, 2014 at 11:39 AM, Mark Miller <[email protected]> wrote:
> I've been sick and am sick, so take it for what it's worth with my head 
> swirling, but I wrote down a few of my thoughts on releases.

Hope you're better Mark :)

> We shouldn't discourage review and reporting back of problems with the 
> release. That is the entire point of the review and vote. We learn which bugs 
> are worth a respin with discussion and consensus.

+1

I actually find it encouraging how many re-spins we've had in recent
releases: I think this is a sign of increased attention / scrutiny.

We should encourage such scrutiny (and, more!), and as issues are
discovered, encourage people to raise them, even if after some
discussion we decide it's not a blocker.

> Potential RMs that don't want to respin may not be the best candidate RM's. 
> Or they should be willing to hand off the reigns for another to respin. That 
> doesn't mean you have to respin or can't argue against it. But it seems like 
> you should be pretty open to the idea if their strong support for it.

+1

> A respin amounts to running a few cmds. It is mostly waiting. And it's easily 
> passed off if your busy. Robert happily picked up the last bits of the 4.6.1 
> release for me when I had to go out of town for a few days. I would do the 
> same for anyone here.

I think if an RM is becoming frustrated running those commands and
waiting then they should "cry uncle" and someone else can easily step
in.

We should try to make the release process as push-button as possible
so there's minimal effort on the RM's part.  We've come a long ways
(the smoke tester, buildAndPushRelease), but we could always improve
automation further.

> I don't think we should try and setup a system that tries to avoid discussion 
> and consensus - I think you just need a fail safe to help ensure it doesn't 
> go on to long.

+1, everyone should feel to raise release issues for discussion on the
vote thread.

Mike McCandless

http://blog.mikemccandless.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to