----- "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. 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. -- R.I.Pienaar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
