Hi,
Thanks Aparna. I'd like to add 2 comments here:
- if you log a new bug against the 0.6 branch, you can use that flag if
you think that it should be fixed in the branch. Do not abuse it of
course. Please set the version to "0.6" for those bugs.
- if you *fix* a bug in the trunk that repros also in the 0.6 branch and
think that the fix is safe and should indeed make it into the branch,
please use this flag to bring it to the attention of the Bug Council.
Add a patch and get it reviewed of course before doing this. I'd add
that bugs tagged with the relnote keyword are prime candidate for this.
Last (and this has nothing to do with 0.6.1), remember to set the
Version field correctly when logging bugs: use "0.6" if you find the bug
in the branch and "0.7" if it's in the trunk. I already saw a couple of
places where it was unclear. Not a big deal right now since the branch
and the trunk are still very much alike but it's going to be more
important with the gap widening. Think about the people triaging the
bugs... Thanks!
Cheers,
- Philippe
Aparna Kadakia wrote:
Now that we have released Chandler 0.6 we can start planning on 0.6.1
milestone. There are a number of semi-critical/major bugs that we
deferred to 0.7 in the last few weeks in the interest of stabilizing
the 0.6 branch and getting a release out on time and in good shape.
I have added a flag called blocking0.6.1 in bugzilla and you can start
nominating bugs for 0.6.1 by setting this flag to ?
The bug council will review the nominated bugs and mark them approved
(+) or denied(-) for the 0.6.1 milestone.
We still don't have a target date for 0.6.1 but it is most likely to
happen after the holidays.
Thanks
Aparna
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
