~ubuntu-branches/ubuntu/wily/cloud-init/wily

1.1.41 by Scott Moser
Import upstream version 0.7.2~bzr795
1
=====================
2
Hacking on cloud-init
3
=====================
4
5
To get changes into cloud-init, the process to follow is:
6
7
* If you have not already, be sure to sign the CCA:
8
9
  - `Canonical Contributor Agreement`_
10
11
* Get your changes into a local bzr branch.
12
  Initialize a repo, and checkout trunk (init repo is to share bzr info across multiple checkouts, its different than git):
13
14
  - ``bzr init-repo cloud-init``
15
  - ``bzr branch lp:cloud-init trunk.dist``
16
  - ``bzr branch trunk.dist my-topic-branch``
17
18
* Commit your changes (note, you can make multiple commits, fixes, more commits.):
19
20
  - ``bzr commit``
21
1.4.24 by Scott Moser
Import upstream version 0.7.6~bzr1016
22
* Check pep8 and test, and address any issues:
1.1.41 by Scott Moser
Import upstream version 0.7.2~bzr795
23
1.4.24 by Scott Moser
Import upstream version 0.7.6~bzr1016
24
  - ``make test pep8``
1.1.41 by Scott Moser
Import upstream version 0.7.2~bzr795
25
26
* Push to launchpad to a personal branch:
27
28
  - ``bzr push lp:~<YOUR_USERNAME>/cloud-init/<BRANCH_NAME>``
29
30
* Propose that for a merge into lp:cloud-init via web browser.
31
32
  - Open the branch in `Launchpad`_
33
34
    - It will typically be at ``https://code.launchpad.net/<YOUR_USERNAME>/<PROJECT>/<BRANCH_NAME>``
35
    - ie. https://code.launchpad.net/~smoser/cloud-init/mybranch
36
37
* Click 'Propose for merging'
38
* Select 'lp:cloud-init' as the target branch
39
40
Then, someone on cloud-init-dev (currently `Scott Moser`_ and `Joshua Harlow`_) will 
41
review your changes and follow up in the merge request.
42
43
Feel free to ping and/or join #cloud-init on freenode (irc) if you have any questions.
44
45
.. _Launchpad: https://launchpad.net
46
.. _Canonical Contributor Agreement: http://www.canonical.com/contributors
47
.. _Scott Moser: https://launchpad.net/~smoser
48
.. _Joshua Harlow: https://launchpad.net/~harlowja