On Feb 25, 2006, at 9:42 PM, Ted Husted wrote:
On 2/25/06, David M Johnson <[EMAIL PROTECTED]> wrote:
I agree that's a problem with the milestone approach.
I'm not seeing the problem. Could someone explain it again in
different terms?
I think the problem is this. Each monthly release adds new features
and usually database schema changes. If each month's release is just
a milestone that may or may not be voted as an official "GA" release
then users will miss important database changes.
Milestones
May - Roller X.Y.1 good release, voted up to GA status
June - Roller X.Y.2 not so good, just considered a alpha
July - Roller X.Y.3 not so good, just considered a beta
August - Roller X.Y.4 good release, voted up to GA status
A user upgrading from X.Y.1 to X.Y.4 needs to incorporate database
schema changes that were made in releases that never got the
official seal of approval. Isn't that a problem?
Maybe we're not in search of a release cycle. Maybe the one we have
is fine. Here's the release cycle that has been in-effect recently
(i.e. this is what Allen and I have been doing).
1) Release planning
- If you want to add a feature to a release, you assign it to
yourself and set the "fix-for" field for the release you want. (see
the roadmap view in JIRA).
2) Development
- If you are working on a feature you mark it as "ongoing" in JIRA
3) Monthly RC1: second to last thursday of each month
- If anybody thinks this month's changes warrant a release, they
ensure that user docs, install docs, change lists and database
scripts are updated and they create RC1.
4) Test week
- Testing focuses on those features marked "ongoing" those that pass
testing are marked as "resolved"
5) Monthly RC2: last thursday of each month
- If somebody rolled an RC last week and testing/fixing went well,
then they create a branch for the release, create RC2 from it and
call for a release vote. We iterate on RCs until voters are satisfied
- While that is happening, mainline development continues in the trunk
- Once release is made, the "resolved" issues are marked as "closed"
in JIRA
- Dave
