| 1 |
--- |
| 2 |
DEVELOPING | 25 +++++++++++++++++++++++++ |
| 3 |
1 file changed, 25 insertions(+) |
| 4 |
|
| 5 |
diff --git a/DEVELOPING b/DEVELOPING |
| 6 |
index 5f15e15..5dfd9b7 100644 |
| 7 |
--- a/DEVELOPING |
| 8 |
+++ b/DEVELOPING |
| 9 |
@@ -160,3 +160,28 @@ The NO example just imports a set of functions from the output module. It is |
| 10 |
somewhat annoying because the import line needs to be modified when functions |
| 11 |
are needed and often unused functions are left in the import line until someone |
| 12 |
comes along with a linter to clean up (does not happen often). |
| 13 |
+ |
| 14 |
+Releases |
| 15 |
+-------- |
| 16 |
+ |
| 17 |
+First create a git tag for this release: |
| 18 |
+ git tag v2.2.8 |
| 19 |
+ |
| 20 |
+Then create the tarball: |
| 21 |
+ ./mkrelease.sh --changelog-rev v2.2.7 --tag 2.2.8 |
| 22 |
+ |
| 23 |
+Unpack the tarball and run tests: |
| 24 |
+ ./runtests.sh |
| 25 |
+Make sure you have all supported python versions installed: |
| 26 |
+ 2.6 2.7 3.2 3.3 |
| 27 |
+ |
| 28 |
+Version bump the ebuild and verify it can re-install itself: |
| 29 |
+ emerge portage |
| 30 |
+ emerge portage |
| 31 |
+ |
| 32 |
+Publish the results (no going back now): |
| 33 |
+ - Push the new git tag |
| 34 |
+ - Upload the tarball |
| 35 |
+ - Commit the new ebuild version |
| 36 |
+ |
| 37 |
+Close the bugs blocking the tracker bug for this release. |
| 38 |
-- |
| 39 |
1.8.4.3 |
Archives