Making a release

From Apertium
Revision as of 21:58, 7 March 2018 by Francis Tyers (talk | contribs)
Jump to navigation Jump to search

En français


This page is out of date as a result of the migration to GitHub. Please update this page with new documentation and remove this warning. If you are unsure how to proceed, please contact the GitHub migration team.

Here are some simple steps to making a release, read the release policy for more information as to when a release should be made. Basically, we have four main stages, "building the package", "testing", "uploading to SourceForge" and "tagging SVN".

Retrieving the version from SVN

Get the latest SVN, or the revision (or date) which you'd like to release. For example to get the version of apertium-oc-ca on the 10th June, 2007, use:

$ svn co -r '{2007-06-10}'

Editing the build files

First update the build files to reflect the new version.




-AC_INIT([apertium-oc-ca], [1.0.2], [<maintainer email>])
-AM_INIT_AUTOMAKE([apertium-oc-ca], [1.0.2], no-define)
+AC_INIT([apertium-oc-ca], [1.0.3], [<maintainer email>])
+AM_INIT_AUTOMAKE([apertium-oc-ca], [1.0.3], no-define)

Building the package


$ ./ 

$ make dist

You should now have a file in the source directory called apertium-oc-ca-1.0.3.tar.gz.

If you have a GPG key, you can sign the release with

$ gpg --detach-sign --armor apertium-oc-ca-1.0.3.tar.gz

This will give you the file apertium-oc-ca-1.0.3.tar.gz.asc that you should upload along with apertium-oc-ca-1.0.3.tar.gz.


Copy the file somewhere temporary, extract it, and test it.

$ mkdir /tmp/test
$ ./configure --prefix=/tmp/test
$ make
$ make install

If you get any errors, go back, fix them in SVN and start again. If the error is in this revision, not in SVN head, then go back to the revision that you checked out and make a note in the ChangeLog of what you changed.

Example contents of ChangeLog:

Wed 20 Jun 2007 08:45:42 BST

  * New release version 1.0.3
  * Updated to fix 'make install' problem. See
    bug #3 in Bugzilla.

Making a release in SourceForge

For this step, you'll need to be an admin on SourceForge (and you need the permission "Allow access to shell server group space (i.e. web space)").

First thing is to log into SourceForge and go to the Apertium project files page.

If there is already a directory for the language pair, then click on it, if not, click on "add folder", and add a new directory. Click on "add file". Select the file on your computer to upload and click "upload". That's it!

You can also upload directly from the terminal like this, assuming your sf username is "foouser":

$ rsync --progress -vh -e ssh apertium-foo-0.9.0.tar.gz

(The "frs" is supposed to be in there; means "file release system" or something like that)

Installing the pair on

1. First update the apy server:

Assuming the tarballs apertium-foo-0.9.0.tar.gz and apertium-foo-bar-0.9.0.tar.gz are in your current dir, do

scp apertium-foo-0.9.0.tar.gz apertium-foo-bar-0.9.0.tar.gz 
cd tarballs
./ apertium-foo-0.9.0.tar.gz
./ apertium-foo-bar-0.9.0.tar.gz
systemctl --user restart apy

2. Possibly update the html-tools server:

If the tarball installed new modes that weren't on before (weren't in before), you'll have to (get spectie to) ssh to the machine running the web page as well and make clean && make -j8 there.

Tagging the release you just made in SVN

In SVN, tagging a release is done using the copy command.

If there is already a module in the /tags/ directory for the module you are packaging, then skip the next step, if not you'll need to do:

$ svn mkdir

Now to tag the release, do:

$ svn copy -r '{2007-06-10}' \
$ svn commit -m "Tagging release"

You can leave out the -r argument if you want to tag the current (HEAD) revision as the release.

Related pages