[Maas-devel] Backporting to 1.5 / Forward-porting to trunk

Julian Edwards julian.edwards at canonical.com
Wed Apr 9 03:35:25 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/04/14 18:37, Mark Shuttleworth wrote:
> 
> In general:
> 
> * we will continue to SRU MAAS to 14.04. Please introduce no new 
> dependencies * any SRU changes will need rigorous test coverage,
> please apply best practice
> 
> Mark


It's worth me re-iterating the development process that we follow, so
that contributors are aware and existing devs get a little reminder:

1. Use your judgement on this, but consider having a
pre-implementation call/irc with a core team member about the change
and to make sure it's heading in a good direction.  Gavin Panella will
be the technical arbiter here.

2. *All* changes must have unit tests in the code, and integration
tests where appropriate (that's an end-to-end test of a feature).

3. A approval vote on a merge proposal from a core team member is good
enough to have permission to land your branch.  Branches may be
self-approved by anyone in maas-maintainers for trivial backports and
obviously trivial bug fixes.

4. Once a change has landed either use "make package" or wait for the
daily build PPA to catch up and QA the changes you made.

5. Verify that the lab tests continue to pass when they run with your
change (they use the daily build PPA package).  Subscribe to the
maas-builds mailing list to get the daily build reports.


Cheers,
J
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlNEv/0ACgkQWhGlTF8G/HerRACfdPBTivsEKGXsjuqoVbzhxIH4
8hkAn3hdUhxlcYc9C2FAnCRB1hhjZYvM
=1meX
-----END PGP SIGNATURE-----




More information about the Maas-devel mailing list