On Sep 15, 2009, at 4:31 PM, R.I.Pienaar wrote:

>
>
> ----- "Markus Roberts" <[email protected]> wrote:
>
>> So if our criterion is " don't push until all tickets marked High or
>> greater are fixed ," and we have the patches for ten Normals, two
>> Highs, a Critical and an Immediate done, approved, tested, and ready
>> to go when out of the blue a new High that we have no idea how to fix
>> comes in do we just not release anything until we solve it?
>>
>> Who, exactly, benefits from such a policy?
>
>
> It would depend on the bug, if the bug is one like 2615 where the  
> master - at this moment this seems to be the situation - actually  
> corrupts data and causes unexpected results, the release shouldn't  
> go out because that renders the release useless.  At present I'd  
> strongly suggest no-one use 0.25.0 for example, if we put out 0.25.1  
> that still has that status then nothing positive comes out of that  
> release.

How does #2615 corrupt data?

This bug just causes services to get restarted when they shouldn't,  
right?  I know this is a problem, but you should only be doing this  
kind of upgrade during a maint. window or something anyway, and  
services should either be able to restart cleanly or should not be  
restarted by Puppet.

I don't mean to downplay the importance of the bug, but we can't  
reproduce it and you thought it was minimal enough that you've  
continued deploying 0.25 on all of your machines even with this bug.

Of course, I really do want to solve the bug, but to do that we have  
to figure out where the bug actually is.

>
> If its not quite that critical, I'd say one where work arounds are  
> documented for that is not too invasive for people, then do the  
> point release.

Markus and I have largely come to an agreement that essentially  
resolves to this.

I think we're going to continue on our quarterly point releases and  
then shoot for monthly point-point releases, but allow a bit of wiggle  
room for important bugs discovered too close to the deadline.  We  
emphatically don't want to hold up releases for bugs that have already  
been open for a week or whatever, but we also don't want to let poor  
timing (e.g., discovery of a bug the day before a release) result in a  
long wait for a fix.

-- 
The truth is that there is nothing noble in being superior to somebody
else. The only real nobility is in being superior to your former self.
     -- Whitney Young
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to