diff --git a/doc/technical/infra/Release.txt b/doc/technical/infra/Release.txt new file mode 100644 index 000000000..2b884fe8c --- /dev/null +++ b/doc/technical/infra/Release.txt @@ -0,0 +1,75 @@ +Release preparation +=================== +:Author: Ichthyo +:Date: Nov 2015 + +we have nothing to show and don't provide public releases yet -- +but we ought to rehearse and practice the release process. +This document contains some hints and a checklist of steps +to perform for a proper release. + +Steps to perform for a release +------------------------------ + + . release prep: clean-up obsolete information + + - Debian package descriptions + - Build-Tutorial + + * building from source + * building the debian way + * contributing + + - technical/build/Dependencies + + . release prep: bump version number + + - `admin/scons/Setup.py` + - `data/config/setup.ini` + - `doc/devel/Doxyfile` + - `doc/devel/Doxyfile.browse` + + . perform a back-merge from the release branch. + + It is relevant not to loose any bugfixes. Especially verify + + - that all ongoing fixes from DEBs and other build activities + are properly represented as patches and committed to the release branch + - that adjustments to platform dependencies are picked up adequately + + . perform the *Release-commit*: + it should mention the kind of the release and the version number. + Typically, with this commit, you'll update some top level stuff in the + source tree, like + + - `README` + - `AUTHORS` + + * also in the ``about'' box in the GTK-UI + * see `setup.ini` + + - check the `LICENSE` file and add new license + declarations and notes, clean obsolete info here. + + . update the *release branch*: ``upgrade current release to ##.##'' + + Make sure the release branch now really reflects current master, maybe + with the omission of some stuff to be kept out of the packages. + Set the *release tag* + + . packaging... + + - merge release -> deb + - verify the package description + - have a look at manpages and similar packaging documents + - update `debian/control` to reflect current version dependencies + - have a look into `debian/rules` (e.g. build flags and similar) + + . delivery + + - use whatever infrastructure is available to build packages. + - verify packages can be installed on a pristine VM + - upload packages to debian depot or commit them to PPAs + - clean-up and discard obsoleted old distributions and packages + + . close the **release ticket** + + diff --git a/wiki/thinkPad.ichthyo.mm b/wiki/thinkPad.ichthyo.mm index fdfca65cd..226343cd2 100644 --- a/wiki/thinkPad.ichthyo.mm +++ b/wiki/thinkPad.ichthyo.mm @@ -2190,9 +2190,10 @@ - + - + + @@ -2584,7 +2585,7 @@ - + @@ -2595,10 +2596,10 @@

- + - - + + @@ -2614,7 +2615,7 @@ - + @@ -2625,13 +2626,14 @@

+ - + @@ -2655,25 +2657,7 @@ - - - - - - - -

- Plattform-Abhängigkeiten -

-

- nochmal gegenchecken -

- - - - - - + @@ -2704,7 +2688,7 @@ - + @@ -2746,8 +2730,8 @@ - - + + @@ -2824,7 +2808,7 @@ - + @@ -2853,9 +2837,11 @@ - + + - + + @@ -2901,7 +2887,7 @@ - + @@ -2920,7 +2906,7 @@ - + @@ -3121,8 +3107,11 @@ - - + + + + + @@ -3130,8 +3119,9 @@ - + + @@ -3222,7 +3212,7 @@ - +