summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorctracey <ctracey@craigtracey.com>2013-01-15 11:36:56 -0500
committerctracey <ctracey@craigtracey.com>2013-01-15 11:36:56 -0500
commita44ca2e095856a2401911ad72a235e6c4d598392 (patch)
tree2b86515c6c19df5daa0122a14ed837e422fc3cae
parent0c38be4ae18e08640269e2f45e9243ea4867153c (diff)
downloadvyos-cloud-init-a44ca2e095856a2401911ad72a235e6c4d598392.tar.gz
vyos-cloud-init-a44ca2e095856a2401911ad72a235e6c4d598392.zip
Add a HACKING file
Adding a HACKING file based upon a message from smoser on the mailing list from 12/12/2012.
-rw-r--r--HACKING27
1 files changed, 27 insertions, 0 deletions
diff --git a/HACKING b/HACKING
new file mode 100644
index 00000000..2111f7e5
--- /dev/null
+++ b/HACKING
@@ -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.