Release early, release often. Not only do I think everything merged in falls under our stated policy, but our policy needs changing.
On Wed, Apr 29, 2009 at 7:42 PM, Michael Harris <[email protected]>wrote: > > On 30/04/2009, Owen Winkler <[email protected]> wrote: > > > > Michael Harris wrote: > >> > >> So, it looks like we're ignoring > >> http://wiki.habariproject.org/en/Release_Policy#Minor_Point_Releases > >> for 0.6.1 then. > > > > In what way? I think the items merged at least qualify under the third > > criterion, if not the prior ones. > > I was away when the 0.6.1 discussion started, and didn't manage to > catch up with it. From what I see that was merged, a few of the > commits are related to data loss (and a couple that could be argued to > be data loss in that deleting data doesn't work), and I don't see any > related to security (though I may have missed that, if I did that's > fine). I don't believe many of them would be blockers, unless we've > changed our criteria in the couple of weeks since we released 0.6. > > The stable releases are for people who want things stable. Upgrading > is a pain. We have an extra responsibility with minor point releases > to try our hardest not to introduce new bugs. That means we should > keep what's included in a minor point release to an absolute minimum. > I know it's nice to get fixes for things out to the community, but > imho that's not enough to warrant inclusion in a point release. > > At least, that's the way I see things. If others see things differently, > okay. > > > If you're referring to merging to the makaanga branch, I think the later > > documentation better applies: > > > http://wiki.habariproject.org/en/Release_Policy#Trunk.2C_Tags.2C_and_Makaanga > > As the policy stands, I disagree. That section is about reaching > stability once we merge to makaanga _before_ a release, not about > minor point releases. > > If the policy doesn't work, fine, let's evolve it. If people want to > say trivial fixes can be included then let's talk about that. As > things stand, I'm not sure why a bunch of these couldn't have waited > until 0.7. > > -- > Michael C. Harris, School of CS&IT, RMIT University > http://twofishcreative.com/michael/blog > IRC: michaeltwofish #habari > > > > --~--~---------~--~----~------------~-------~--~----~ 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/habari-dev -~----------~----~----~----~------~----~------~--~---
