root / CONTRIBUTING @ master
History | View | Annotate | Download (1.2 kB)
| 1 |
Some development notes about the Lunch project |
|---|---|
| 2 |
|
| 3 |
The release process |
| 4 |
------------------- |
| 5 |
|
| 6 |
Update the documentation if needed: |
| 7 |
|
| 8 |
* scripts/lunch |
| 9 |
* scripts/lunch-slave |
| 10 |
* man_lunch.txt |
| 11 |
* README |
| 12 |
|
| 13 |
Make sure the version number is the next release's: |
| 14 |
|
| 15 |
* scripts/lunch-slave |
| 16 |
* lunch/__init__.py |
| 17 |
|
| 18 |
Run the unit tests:: |
| 19 |
|
| 20 |
trial lunch |
| 21 |
|
| 22 |
Update the release notes: |
| 23 |
|
| 24 |
* NEWS |
| 25 |
|
| 26 |
Update the ChangeLog:: |
| 27 |
|
| 28 |
git log --pretty=medium > ChangeLog |
| 29 |
|
| 30 |
Create the tag and a tarball: |
| 31 |
|
| 32 |
* Make sure you are in the right branch. (develop) |
| 33 |
* Commit any change:: |
| 34 |
|
| 35 |
git co -b release-0.4.0 (in this example, we release 0.4.0) |
| 36 |
|
| 37 |
* Increase the version number to the next even micro version number (see "Files with version number") |
| 38 |
* Make any additional change |
| 39 |
* Do (wisely and step by step) this:: |
| 40 |
|
| 41 |
git co master |
| 42 |
git merge --no-ff release-0.4.0 |
| 43 |
git tag 0.4.0 |
| 44 |
./utils/make-tarball.sh 0.4.0 |
| 45 |
git co develop |
| 46 |
git merge --no-ff release-0.4.0 |
| 47 |
git branch -d release-0.4.0 |
| 48 |
git push --tags origin master:master develop:develop |
| 49 |
|
| 50 |
* Increase the version number to the next odd micro version number (never to be released) (0.4.1 in this example) |
| 51 |
* Commit with "post-release version bump" message. |
| 52 |
|
| 53 |
|
| 54 |
Files with version number |
| 55 |
------------------------- |
| 56 |
|
| 57 |
* scripts/lunch-slave |
| 58 |
* lunch/__init__.py |
| 59 |
|