"Fossies" - the Fresh Open Source Software Archive
Member "relax-5.0.0/minfx/doc/Release_Checklist" (25 Aug 2020, 3219 Bytes) of package /linux/privat/relax-5.0.0.src.tar.bz2:
As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard
) with prefixed line numbers.
Alternatively you can here view
the uninterpreted source code file.
1 * Make a copy of the current head to the tags directory using a command such as:
3 $ svn cp -F svn_msg svn+ssh://email@example.com/svn/minfx/trunk svn+ssh://firstname.lastname@example.org/svn/minfx/tags/1.0.5
5 In the commit message file 'svn_msg', have a header line which says 'Minfx version 1.0.5.', followed by a short description of the release.
9 * Checkout the tagged version with:
11 $ svn co svn+ssh://email@example.com/svn/minfx/tags/1.0.5
15 * Review the SVN logs and add an entry into the CHANGES file for the current release. Create three sections titled 'Features', 'Changes', and 'Bugfixes'. Commit the changes and then port the revision back into the main line.
19 * Change the version number in both 'setup.py' and 'minfx.__init__.__version__', and commit the changes.
23 * Generate the distribution files by typing:
25 $ python setup.py sdist --formats=bztar,gztar,zip
27 and generate their GPG signatures by going into the dist/ directory and typing:
29 $ gpg --detach-sign --default-key xxx minfx-1.0.1.tar.bz2
30 $ gpg --detach-sign --default-key xxx minfx-1.0.1.tar.gz
31 $ gpg --detach-sign --default-key xxx minfx-1.0.1.zip
33 where xxx is the name of your private GPG key.
36 * Move the distribution files and their signatures to the mirror directory for the minfx download site. This directory should contain all the files and directories accessible from 'http://download.gna.org/minfx/'. First make sure the mirror directory contains all of the files so that the next command does not accidentally delete files:
38 $ rsync -av --progress --no-perms --rsh="ssh" firstname.lastname@example.org:/upload/minfx/ .
40 Then rsync the entire directory contents to http://download.gna.org/upload/minfx/ using the command:
42 $ rsync --delete -av --no-perms --rsh="ssh" . email@example.com:/upload/minfx/
46 * Create the API documentation for the current version with the command:
48 $ ./doc/api.sh
50 Replace the old API documentation in the http://home.gna.org/minfx SVN repository (http://svn.gna.org/viewcvs/minfx/website) and commit the new files.
54 * Add the version number to the bug tracker field 'Release' at https://gna.org/bugs/admin/field_values.php?group=minfx.
58 * Post the release message to the minfx-announce mailing list and as a news item on the minfx Gna! website.
60 On the minfx-announce mailing list, write a detailed and full description of the release. Also add a paragraph with links for downloading the release. At the end, add a section titled 'The full list of changes is:' and copy and paste the part of the CHANGES file for this release. Include links to the trackers in the full list of changes.
62 For the news item, firstly cut and paste the mailing list message. Create three sections using the Savane markup (recipe #236). Call these = Description =, = Download =, and = Full list of changes =. For the last section, use the subtitles == Features == , == Changes == , and == Bugfixes ==. The items in this section start with '* ' to create an unnumbered list. Strip all leading whitespace from the full list of changes and remove all the links to the trackers (as these will be automatically created).
66 * Update the version number in the FSF directory (http://directory.fsf.org/wiki/Minfx).