On Jul 27, 2009, at 8:33 AM, Peter Meier wrote:
> > Hi > >> Disclaimer: I don't know what the goals are with respect to release >> cycles, so >> my comments are based on a 'get 0.25 done as soon as possible' >> mindset. >> >> Would it be reasonable for this *not* go into 0.25 (which is almost >> ready for >> release) but instead go into 0.26, and that 0.26 *only* contain >> this, the >> transaction/event handling changes, and bug fixes. > > I dunno as well about feature release cycles. However taken the > release cycle for 0.25 since the last 0.24 release and if somebody > tests it and it's working fine, I would vote to get it into 0.25. > > Maybe simply to feed the crowd... ;) > > If the release cycle for the next major release is rather short (a few > (2-3) months) I think it can also go into 0.26 . Once 0.25 is out we'll be back on our regular quarterly release schedule. 0.25 was a complete anomaly, and I'll be doing my best to make sure it stays that way. -- When I die, I want go out just like my grandfather, in his sleep, peaceful and quiet...not kicking and screaming like the other guys in his car. --------------------------------------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
