[Maas-devel] All branches must be linked to bugs/blueprints

Julian Edwards julian.edwards at canonical.com
Tue Jul 8 04:48:00 UTC 2014


Greetings,

Please make sure *all* of your branches are linked to bugs and/or
blueprints from now on.  The only exception to this rule is any branch
that changes things in the development environment such as lint fixes or
refactorings.

Reviewers - please enforce this rule, it applies to 1.5, 1.6 (when I cut
it) and trunk.

The reason for this is that we need to be stricter about keeping to the
commitments required for any minor release exception(s) to upload new
releases to 14.04.

Also, it makes it many times harder for me, your friendly neighbourhood
release manager, to reconcile and track changes in release branches when
I produce release notes.

A good tip is to use the --fixes lp:NNNNN argument to bzr commit.  This
gives you a couple of nice things:

 1. LP will automatically link the bug to the branch for you after you
push up a revision that has --fixes

 2. Tarmac will mark the bug fix-committed when it lands the branch.

Note that #2 doesn't happen if you use LP to manually do the bug-branch
link.

Cheers
J




More information about the Maas-devel mailing list