Changes

Jump to: navigation, search

What to do for a release

25 bytes added, 06:00, 14 October 2007
m
minor cleanup
==Translations==
* announce the intent to release on the <tt>[email protected] </tt> mailing list; ask that no further changes be committed to svn* build what should be the last final <tt>gramps.pot</tt> file:
cd po
make gramps.pot
* commit the new <tt>gramps.pot</tt> file to svn
* ask for all [[Translating GRAMPS|translators]] on <tt>[email protected] </tt> and <tt>[email protected] </tt> to update the <tt>.po</tt> files; plan to release about 1 to 2 weeks after this date
* ask for translators to e-mail their <tt>.po</tt> files to you; not all translators have svn access; expect to spend a bit of time checking in <tt>.po</tt> files
* ask people to download and test from http://gramps-project.org/test/
==Make releasing on SourceForge siteMaking the release available==
* note the names of [[previous releases]]
* upload the tarball by anonymous ftp to ftp://upload.sourceforge.net/incoming/
* add uploaded file(s) to the release by checking the appropriate check button and then clicking the "Add Files and/or Refresh View" button
* set architecture and the file type, click "Update/Refresh"
* send notifications to the sourceforge subscribers of gramps
==Following Once the tarball releaseis available==* announce on <tt>[email protected]</tt>, as well as <tt>gramps-devel @lists.sourceforge.net</tt> and user list<tt>[email protected]</tt>
* update news section on this wiki
* change update reference from old to the new version on the [[Installation]] page
==Update the version number==

Navigation menu