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