User Tools

Site Tools


geda:release_engineering

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
geda:release_engineering [2012/11/17 14:05]
peter-b Updated wiki update process (without dodgy scripts)
geda:release_engineering [2016/04/26 06:12] (current)
vzh Slightly tweaked explanation.
Line 12: Line 12:
 Here is a list of steps that are taken every time when creating a new gEDA/gaf release: Here is a list of steps that are taken every time when creating a new gEDA/gaf release:
  
-  * In the toplevel configure.ac file update the package version in the AC_INIT macro, the date in the AX_GIT_VERSION macro, and update ​libgeda'​s ​shared library ​version (libgeda'​so version ​should follow what is described in [[ http://​sourceware.org/​autobook/​autobook/​autobook_91.html | Autobook'​s library versioning]] chapter).+  * In the toplevel configure.ac file update the package version in the AC_INIT macro, the date in the AX_GIT_VERSION macro, and update shared library ​versions of the package libraries, currently //libgeda// (AX_LIBGEDA) ​ and //​libgedacairo//​ (AX_LIBGEDACAIRO) (their ​''.so''​ versions ​should follow what is described in [[http://​sourceware.org/​autobook/​autobook/​autobook_91.html | Autobook'​s library versioning]] chapter).
   * Update the toplevel NEWS file with a summary of all the changes in the new release. ​ The NEWS file forms the basis for the release notes.   * Update the toplevel NEWS file with a summary of all the changes in the new release. ​ The NEWS file forms the basis for the release notes.
   * Manually run all tests. ​ gnetlist has a nice set of regression tests in gnetlist/​tests. ​ gsymcheck also has a nice set of regression tests in gsymcheck/​tests. ​ Open up all schematics in gschem/​examples and gschem/​tests. ​ You can do this by running the following in the toplevel directory:   * Manually run all tests. ​ gnetlist has a nice set of regression tests in gnetlist/​tests. ​ gsymcheck also has a nice set of regression tests in gsymcheck/​tests. ​ Open up all schematics in gschem/​examples and gschem/​tests. ​ You can do this by running the following in the toplevel directory:
Line 37: Line 37:
  
   * Commit all of the above changes (preferably in between each step)   * Commit all of the above changes (preferably in between each step)
-  * To build the distribution tarball (and verify all tests on the contained files) run:  +  * To build the distribution tarball (and verify all tests on the contained files) run:
  
 <​code>​ <​code>​
-        make distcheck ​  ​+        make distcheck
 </​code>​ </​code>​
  
 and make sure it completes without any errors. ​ After this is complete you will find the distribution tarball in the toplevel directory (named geda-gaf-VERSION.tar.gz). and make sure it completes without any errors. ​ After this is complete you will find the distribution tarball in the toplevel directory (named geda-gaf-VERSION.tar.gz).
   * Copy the distribution tarball some place else along with the toplevel README (which should be renamed to gEDA-gaf-VERSION-README.txt).   * Copy the distribution tarball some place else along with the toplevel README (which should be renamed to gEDA-gaf-VERSION-README.txt).
-  * Create a file the md5sum for the toplevel tarball. ​+  * Create a file the md5sum for the toplevel tarball.
 <​code>​ <​code>​
         md5sum -b geda-gaf-1.5.3.tar.gz > geda-gaf-1.5.3.md5sum         md5sum -b geda-gaf-1.5.3.tar.gz > geda-gaf-1.5.3.md5sum
Line 55: Line 55:
         git tag -a 1.5.3-20090829         git tag -a 1.5.3-20090829
 </​code>​ </​code>​
-  * Push all the commits to the main repository. ​ If you are on a branch the command should be: +  * Push all the commits to the main repository. ​ If you are on a branch the command should be:
 <​code>​ <​code>​
         git push origin remote_branch_name         git push origin remote_branch_name
Line 67: Line 67:
   * Write up release notes and send pointer to mailing lists (named: geda-gaf-VERSION-releasenotes.html)   * Write up release notes and send pointer to mailing lists (named: geda-gaf-VERSION-releasenotes.html)
   * Update news update the sources download pages on the website with links to the new version   * Update news update the sources download pages on the website with links to the new version
-  * Update the geda:​todos ​page moving ​the release ​into the historical todos page.+  * Update the [[geda:todos]] removing ​the release ​information.
   * Done!   * Done!
- 
- 
- 
- 
- 
  
geda/release_engineering.1353179123.txt.gz ยท Last modified: 2012/11/17 14:05 by peter-b