Making a release - Revision history

Unhammer: remove /* Making a release in SourceForge */

2021-04-26T09:59:40Z

remove Making a release in SourceForge

Unhammer at 13:10, 11 March 2019

2019-03-11T13:10:43Z

Unhammer: /* Making a release in SourceForge */

2019-03-11T13:10:16Z

Making a release in SourceForge

Unhammer: git

2019-03-11T12:28:52Z

git

Francis Tyers at 21:58, 7 March 2018

2018-03-07T21:58:40Z

Unhammer: /* Installing the pair on apertium.org */

2016-06-07T20:24:58Z

Installing the pair on apertium.org

Unhammer: /* Making a release in SourceForge */

2016-06-07T20:24:25Z

Making a release in SourceForge

Unhammer: /* Making a release in SourceForge */

2016-06-07T20:15:51Z

Making a release in SourceForge

Unhammer: /* Making a release in SourceForge */

2016-06-07T20:14:43Z

Making a release in SourceForge

Unhammer: /* Tagging the release you just made in SVN */

2016-01-23T22:11:04Z

Tagging the release you just made in SVN

@@ Line 53: / Line 53: @@
 If you get any errors, go back, fix them in git, push and start again.
-==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 [https://sourceforge.net/projects/apertium/files/ 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":
-<pre>
-$ rsync --progress -vh -e ssh apertium-foo-0.9.0.tar.gz foouser@frs.sourceforge.net:/home/frs/project/apertium/apertium-foo/
-</pre>
-(The "frs" is supposed to be in there; means "file release system" or something like that)
 ==Installing the pair on apertium.org==

@@ Line 68: / Line 68: @@
 </pre>
 (The "frs" is supposed to be in there; means "file release system" or something like that)
-==Making a release on github==
-After tagging, you can
-* go to https://github.com/apertium/apertium-foo-bar/releases/
-* and pick your tag
-* and click "Edit release",
-* and upload your tarball (and signature, if you did that)
 ==Installing the pair on apertium.org==
@@ Line 105: / Line 97: @@
 The above will tag the current commit; you can change HEAD for some commit hash or branch if you want to tag that instead.
+==Making a release on github==
+After tagging, you can
+* go to https://github.com/apertium/apertium-foo-bar/releases/
+* and pick your tag
+* and click "Edit release",
+* and upload your tarball (and signature, if you did that)

@@ Line 68: / Line 68: @@
 </pre>
 (The "frs" is supposed to be in there; means "file release system" or something like that)
+==Making a release on github==
+After tagging, you can
+* go to https://github.com/apertium/apertium-foo-bar/releases/
+* and pick your tag
+* and click "Edit release",
+* and upload your tarball (and signature, if you did that)
 ==Installing the pair on apertium.org==

@@ Line 3: / Line 3: @@
 {{TOCD}}
 {{Github-migration-check}}
-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".
+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 in git".
-==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 <code>apertium-oc-ca</code> on the 10th June, 2007, use:
-<pre>
-$ svn co -r '{2007-06-10}' https://apertium.svn.sourceforge.net/svnroot/apertium/trunk/apertium-oc-ca
-</pre>
 ==Editing the build files==
@@ Line 16: / Line 10: @@
 First update the build files to reflect the new version.
-Edit Makefile.am:
+Edit Makefile.am and delete any lines like
 <pre>
--VERSION=1.0.2
+RELEASE=0.9
-+VERSION=1.0.3
+VERSION=0.9.7
 </pre>
+(Makefile.am shouldn't have any version info.)
 Edit configure.ac:
 <pre>
--AC_INIT([apertium-oc-ca], [1.0.2], [<maintainer email>])
+-AC_INIT([Apertium Foolish-Barman], [0.9.7], [maintainer@domain.org], [apertium-foo-bar], [http://wiki.apertium.org/wiki/Apertium-foo-bar])
++AC_INIT([Apertium Foolish-Barman], [1.0.0], [maintainer@domain.org], [apertium-foo-bar], [http://wiki.apertium.org/wiki/Apertium-foo-bar])
--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)
 </pre>
 ==Building the package==
-Run autogen.sh:
 <pre>
 $ ./autogen.sh
 $ make dist
 </pre>
-You should now have a file in the source directory called <code>apertium-oc-ca-1.0.3.tar.gz</code>.
+You should now have a file in the source directory called <code>apertium-foo-bar-1.0.0.tar.gz</code>.
 If you have a GPG key, you can sign the release with
 <pre>
-$ gpg --detach-sign --armor apertium-oc-ca-1.0.3.tar.gz
+$ gpg --detach-sign --armor apertium-foo-bar-1.0.0.tar.gz
 </pre>
-This will give you the file <code>apertium-oc-ca-1.0.3.tar.gz.asc</code> that you should upload along with <code>apertium-oc-ca-1.0.3.tar.gz</code>.
+This will give you the file <code>apertium-foo-bar-1.0.0.tar.gz.asc</code> that you should upload along with <code>apertium-foo-bar-1.0.0.tar.gz</code>.
 ==Testing==
@@ Line 59: / Line 52: @@
 </pre>
-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.
+If you get any errors, go back, fix them in git, push and start again.
-Example contents of ChangeLog:
-<pre>
-Wed 20 Jun 2007 08:45:42 BST
-  * New release version 1.0.3
-  * Updated Makefile.am to fix 'make install' problem. See
-    bug #3 in Bugzilla.
-</pre>
 ==Making a release in SourceForge==
@@ Line 103: / Line 87: @@
 If the tarball installed new modes that weren't on apertium.org before (weren't in http://apy.projectjj.com/listPairs before), you'll have to (get spectie to) ssh to the machine running the apertium.org web page as well and <code>make clean && make -j8</code> there.
-==Tagging the release you just made in SVN==
+==Tagging the release you just made in git==
-In SVN, tagging a release is done using the <code>copy</code> command.
+In git, tagging a release is done using the <code>git tag</code> command, see <code>git help tag</code>.
-If there is already a module in the <code>/tags/</code> directory for the module you are packaging, then skip the next step, if not you'll need to do:
 <pre>
+$ git tag -s -m "v1.0.0 released" v1.0.0 HEAD
-$ svn mkdir https://svn.code.sf.net/p/apertium/svn/tags/apertium-oc-ca
+$ git push --tags
 </pre>
+The above will tag the current commit; you can change HEAD for some commit hash or branch if you want to tag that instead.
-Now to tag the release, do:
-<pre>
-$ svn copy -r '{2007-06-10}'  https://svn.code.sf.net/p/apertium/svn/trunk/apertium-oc-ca \
- https://svn.code.sf.net/p/apertium/svn/tags/apertium-oc-ca/release-1.0.3
-$ svn commit -m "Tagging release"
-</pre>
-You can leave out the -r argument if you want to tag the current (HEAD) revision as the release.

@@ Line 2: / Line 2: @@
 {{TOCD}}
+{{Github-migration-check}}
 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".

@@ Line 100: / Line 100: @@
 . Possibly update the html-tools server:
-If the tarball installed new modes that weren't on apertium.org before, you'll have to (get spectie to) ssh to the machine running the apertium.org web page as well and <code>make clean && make -j8</code> there.
+If the tarball installed new modes that weren't on apertium.org before (weren't in http://apy.projectjj.com/listPairs before), you'll have to (get spectie to) ssh to the machine running the apertium.org web page as well and <code>make clean && make -j8</code> there.
 ==Tagging the release you just made in SVN==

@@ Line 82: / Line 82: @@
 $ rsync --progress -vh -e ssh apertium-foo-0.9.0.tar.gz foouser@frs.sourceforge.net:/home/frs/project/apertium/apertium-foo/
 </pre>
-(The "frs" is supposed to be in there, means "file release system" or something like that)
+(The "frs" is supposed to be in there; means "file release system" or something like that)
+==Installing the pair on apertium.org==
+. 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
+<pre>
+scp apertium-foo-0.9.0.tar.gz apertium-foo-bar-0.9.0.tar.gz apertium@oqaa.projectjj.com:~/tarballs/
+ssh apertium@oqaa.projectjj.com
+cd tarballs
+./install-tarball.sh apertium-foo-0.9.0.tar.gz
+./install-tarball.sh apertium-foo-bar-0.9.0.tar.gz
+systemctl --user restart apy
+</pre>
+. Possibly update the html-tools server:
+If the tarball installed new modes that weren't on apertium.org before, you'll have to (get spectie to) ssh to the machine running the apertium.org web page as well and <code>make clean && make -j8</code> there.
 ==Tagging the release you just made in SVN==

@@ Line 96: / Line 96: @@
 You can leave out the -r argument if you want to tag the current (HEAD) revision as the release.
+==Related pages==
+* [[Packaging]] (Debian etc.)
+* [[Release policy]]
 [[Category:Documentation]]