cloud-init-dev team mailing list archive
-
cloud-init-dev team
-
Mailing list archive
-
Message #00197
[Merge] lp:~craigtracey/cloud-init/add-hacking-info into lp:cloud-init
Craig Tracey has proposed merging lp:~craigtracey/cloud-init/add-hacking-info into lp:cloud-init.
Requested reviews:
cloud init development team (cloud-init-dev)
Related bugs:
Bug #1099919 in cloud-init: "Add HACKING information"
https://bugs.launchpad.net/cloud-init/+bug/1099919
For more details, see:
https://code.launchpad.net/~craigtracey/cloud-init/add-hacking-info/+merge/143355
Add a HACKING file
Adding a HACKING file based upon a message from smoser on the mailing list from 12/12/2012.
--
https://code.launchpad.net/~craigtracey/cloud-init/add-hacking-info/+merge/143355
Your team cloud init development team is requested to review the proposed merge of lp:~craigtracey/cloud-init/add-hacking-info into lp:cloud-init.
=== added file 'HACKING'
--- HACKING 1970-01-01 00:00:00 +0000
+++ HACKING 2013-01-15 16:50:33 +0000
@@ -0,0 +1,27 @@
+To get changes into cloud-init, the process to follow is:
+
+ * get your changes into a local bzr branch:
+ # init a repo, and checkout trunk (init repo is to share bzr info
+ # across multiple checkouts, its different than git).
+ bzr init-repo cloud-init
+ bzr branch lp:cloud-init trunk.dist
+ bzr branch trunk.dist my-topic-branch
+ * commit your changes
+ bzr commit
+ # note, you can make multiple commits, fixes, more commits.
+ * check pylint and pep8 and test , and address issues
+ make test pylint pep8
+ * push to launchpad to a personal branch:
+ bzr push lp:~<YOUR_USERNAME>/cloud-init/<BRANCH_NAME>
+ * propose that for a merge into lp:cloud-init via web browser
+ # open the branch in launchpad, it will be at:
+ # https://code.launchpad.net/<YOUR_USERNAME>/<PROJECT>/<BRANCH_NAME>
+ # for example:
+ # https://code.launchpad.net/~smoser/cloud-init/mybranch
+ click 'propose for merging'
+ select 'lp:cloud-init' as the target branch
+
+ Then, someone on cloud-init-dev (currently Scott Moser and Joshua Harlow) will
+review your changes and follow up in the merge request.
+
+ Feel free to ping #cloud-init on freenode if you have any questions.