On Wed, Apr 29, 2009 at 7:42 PM, Michael Harris <[email protected]> wrote: > 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.
I think there's a slippery slope here. Some things merit inclusion in a point release because they demonstrably improve the overall quality of the product. Things like spelling corrections, removal of cruft (unused images, etc). Other minor or trivial bug fixes are worth considering because they improve the user experience without jeopardizing a functioning installation. I don't think such minor bugfixes should trigger a minor point release; but to not fix little things along the way seems a disservice to our users. > 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. They could have waited until 0.7, but why? Some of these little fixes will make Habari a better product for users right now. I've updated the Release Policy wiki page: http://wiki.habariproject.org/en/Release_Policy I would appreciate feedback on the new text. It should not be considered set in stone. Thanks, Scott --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
