[Chandler-dev] 0.7.2 bugs (or more generally, bugs targeted for release after svn branched)

[Heikki Toivonen]

There has been a little confusion about what the process is for bugs
that were still targeted for 0.7.2 after we created the 0.7.2 branch and
Philippe moved all non-blocking bugs to 0.7.3.

Briefly, if you are holding a 0.7.2 blocker, you need to check the fix
in to trunk and merge it into the 0.7.2 branch as well. Only when the
fix has been checked into both places should you mark the bug fixed.
Please include in the comments information about the revisions when it
went to trunk and branch.

To get the branch sources, you can issue command such as:

svn co
svn+ssh://svn.osafoundation.org/svn/chandler/branches/0.7.2/chandler
chandler-0.7.2

Then, to merge a change from trunk, say r15673:

svn merge -r 15672:15673
svn+ssh://svn.osafoundation.org/svn/chandler/trunk/chandler

Then run tests and checkin. Testing is important because we don't have
tinderboxes for these short lived branches.

This process applies to future releases as well.

There may be a brief period of time when we create a branch but have not
yet moved the non-blockers to the next release, when you should check
with bug council whether or not you should check a fix to the branch as
well. Philippe or someone from the bug council should typically do that
bug scrub within a day of branch creation, and an email should go out
when that scrub has been done.

-- 
  Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20071106/95dda0df/signature.pgp