On 8/27/08, Christopher Arndt <[EMAIL PROTECTED]> wrote: > > > Sounds like a good plan, though I think a quarterly release schedule > would be enough as well and might be easier to handle with the few > resources we have.
Quarterly is even better for me :) Security releases could always be on-demand anyway. > > > This means only _fixes_ go into the 1.0 branch from now on, with > > unittests. And the time based release will make sure we can have those > > fixes on a regular basis. > > > I'd like for us to try to have a closer definition of what a "fix" that > should go into 1.0.X maintenance releases constitutes. To get the > discussion about this started, here's a little list of different types > of changes: > > 1. Documentation typo fixes > 2. Documentation improvements > 3. Code style fixes > 4. Refactoring > > 5. Isolated bug fixes > 6. Bug fixes that change code structure or logic > 7. Security fixes > > 8. New features > > IMHO, only fixes of type 5 & 7 and maybe 6 should go into 1.0.X > maintenance releases. The distinction between 5 & 6 and 8 would have to > be decided on a case-by-case basis, depending on the criticality of the bug. +1 for this distinction and filter. 6 would only be accepted in 1.0.x if the bug is really a big one and it does not force a major refactoring. I feel that 1.1 is retro compatible enough that we could have nearly all 1.0.3+ apps migrated in a breeze anyway. Florent. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
