twl at osafoundation.org
Tue Aug 14 13:54:30 PDT 2007
So the actual mechanics of the branching aside, here are some things
to keep in mind about the 0.7.x series:
1. These are going to be bug fix only releases - no new features, and
no refactorings unless *absolutely* necessary for a bug fix. The
goal of the 0.7.x series is to continue to stabilize the software
once it has been deployed. Anything that looks remotely like a
feature should be targeted for 0.8. The sole exception that I can
think of is making Safari work, and I don't think that will be the
target for 0.7.1
2. Releasing these on a regular schedule is important. One way of
making sure that we do this is to restrict the number of changes that
3. I expect prioritization of fixes to go in these releases to be
driven more by QA and PPD than by engineering. We have not yet gone
through the exercise of prioritizing any bugs for 0.7.1, so you
should look at 0.7.1 as a holding bin for bugs that will get spread
out over 0.7.1, 2, 3, 4, etc.
On Aug 14, 2007, at 10:30 AM, Travis Vachon wrote:
> Hi folks
> Now that we're rolling a ZBR I'm excited to start working on 0.7.1
> bugs. I'd like to be able to check my work in, so there are a few
> questions that need answers:
> 1) What's our branching strategy for the 0.7.x releases?
> a) Branches off trunk that are merged back to trunk at the time
> of the "dot release"?
> b) Branches off a "0.7" branch that is kept "0.7 pristine",
> merging the branches back to trunk at the time of "dot releases"?
> c) Other?
> 2) What about the work Brian's already doing on 0.8? When does that
> get merged back to trunk?
> It would be nice to set a precedent that everyone is happy (or at
> least not unhappy) with during the next month or so, so my
> intention with this thread is to come to that consensus.
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
More information about the cosmo-dev