GNUstep release procedure - Revision history

Rfm at 08:06, 30 May 2024

2024-05-30T08:06:10Z

Rfm at 07:09, 16 January 2007

2007-01-16T07:09:02Z

Fedor at 19:44, 15 January 2007

2007-01-15T19:44:05Z

Fedor: clearer instructions

2006-09-14T03:03:05Z

clearer instructions

Fedor at 03:34, 28 August 2006

2006-08-28T03:34:28Z

Fedor: /* Preparation */

2006-08-28T03:33:31Z

Preparation

Stefan Urbanek at 11:33, 17 March 2005

2005-03-17T11:33:54Z

Tarzeau: /* Packaging */

2005-02-26T16:58:16Z

Packaging

Stefan Urbanek at 09:18, 25 February 2005

2005-02-25T09:18:48Z

Stefan Urbanek at 09:18, 25 February 2005

2005-02-25T09:18:28Z

New page

The release procedure describes steps required to create new release of GNUstep and its packages.

Requirements:
* it should be possible to create a release from clean CVS checkout

Steps:
# do pure GNUstep CVS checkout
# make sure that all required release tests passed
# increase appropriate version number
# create the package
# upload the package
# notify packagers on other platforms
# announce the release

If the packages are used by the GNUstep umbrella package (runtime or development environment), then the ubrella package should be released too.

== Preparation ==

It is desired that the release is made from CVS checkout. The release should correspond to a tagged state in the CVS.

Also it is required that all release test passed. If not, the release should not be created. For more information about the tests see [[Quality assurance]].

Follow standard versioning guidelines.

== Packaging ==

The .tar.gz package should be created and put into appropriate directonr in ftp://ftp.gnustep.org/pub/gnustep.

Concerning binary packages, the person responsible for the release should notify all packagers for different platforms.

''FIXME: add a list in the following form: ''

GNUstep Package | Packager | notify email addres (it should be a list)

== Announcement ==

[http://groups-beta.google.com/group/gnu.gnustep.announce/browse_thread/thread/4dd4529968665bd6/75f5adfbd644cce9?_done=%2Fgroup%2Fgnu.gnustep.announce%3F&_doneTitle=Back+to+topics&_doneTitle=Back&&d#75f5adfbd644cce9 example of an announcement]

''FIXME: upload an announcement template for all core GNUstep packages here.''

@@ Line 18: / Line 18: @@
 . Tag the release
-  make svn-tag
+  make git-tag
+ git push --tags
 . Make a source distribution
-  make svn-dist
+  make git-dist
 . Administrative stuff (Note: Admin-only scripts that I use to make this easier are in brackets):
@@ Line 35: / Line 34: @@
 * Make an announcement on info-gnustep@gnu.org, etc
-If the packages are used by the GNUstep umbrella package (runtime or development environment), then the ubrella package should be released too.
+If the packages are used by the GNUstep umbrella package (runtime or development environment), then the umbrella package should be released too.
 == Preparation ==
-It is desired that the release is made from SVN checkout. The release should correspond to a tagged state in the SVN.
+It is desired that the release is made from git checkout. The release should correspond to a tagged state in the git.
 Also it is required that all release test passed. If not, the release should not be created. For more information about the tests see [[Quality assurance]].

← Older revision		Revision as of 07:09, 16 January 2007
Line 19:		Line 19:

	make svn-tag		make svn-tag
		+
		+	(or 'make svn-tag-stable' if you are making a bugfix release from a stable branch rather than a main release from trunk).

	6. Make a source distribution		6. Make a source distribution

@@ Line 1: / Line 1: @@
 Steps for releasing the GNUstep core libraries (as well as others):
-. Make sure news.texi and ReleaseNotes.gsdoc files are updated (or NEWS, ANNOUNCE, etc if it is a simple package).
+. Make sure news.texi and ReleaseNotes.gsdoc files are updated (or NEWS, ANNOUNCE, etc if it is a simple package). If the release is on a stable branch, also update these on the main branch so they are available to read in future releases.
 . Update the 'Version' file with the new version or make sure the top-level GNUmakefile has VERSION set if there is not a separate Version file.
@@ Line 26: / Line 26: @@
 . Administrative stuff (Note: Admin-only scripts that I use to make this easier are in brackets):
-* Sign the packages [gstep-sign] or just use gpg --detach-sign package.tar.gz
+* Sign the packages. Use gpg --detach-sign package.tar.gz [gstep-sign]
-* Upload packages to ftp.gnustep.org [gstep-update, gstep-upload]
+* Upload packages to ftp.gnustep.org, into the incoming directory [gstep-update].
-* Install the documentation and copy it to the web repository [update_documentation]
+* Install the documentation and copy it to the web repository [update_documentation].
 * Update the index.html and resources/downloads.php pages with the news.
 * Commit the web repository.
 * Make an announcement on info-gnustep@gnu.org, etc
 If the packages are used by the GNUstep umbrella package (runtime or development environment), then the ubrella package should be released too.

@@ Line 1: / Line 1: @@
 Steps for releasing the GNUstep core libraries (as well as others):
-. Make sure news.texi and ReleaseNotes.gsdoc files are updated
+. Make sure news.texi and ReleaseNotes.gsdoc files are updated (or NEWS, ANNOUNCE, etc if it is a simple package).
-. Update the 'Version' file with the new version
+. Update the 'Version' file with the new version or make sure the top-level GNUmakefile has VERSION set if there is not a separate Version file.
-. Update the documentation and release notes in the main directory:
+. core libraries: Update the documentation and release notes in the main directory:
   cd Documentation
@@ Line 24: / Line 24: @@
   make svn-dist
-. Administrative stuff (scripts that I use to make this easier are in brackets):
+. Administrative stuff (Note: Admin-only scripts that I use to make this easier are in brackets):
-* Make RPMS or whatever [gstep-distribute]
+* Sign the packages [gstep-sign] or just use gpg --detach-sign package.tar.gz
 * Upload packages to ftp.gnustep.org [gstep-update, gstep-upload]
 * Install the documentation and copy it to the web repository [update_documentation]

@@ Line 18: / Line 18: @@
 . Tag the release
-  make cvs-tag
+  make svn-tag
 . Make a source distribution
-  make cvs-dist
+  make svn-dist
 . Administrative stuff (scripts that I use to make this easier are in brackets):

@@ Line 31: / Line 31: @@
 ''FIXME: add a list in the following form: ''
-  GNUstep Package | Packager | notify email addres (it should be a list)
+  GNUstep Package | Packager | notify email address (it should be a list)
 == Announcement ==

← Older revision		Revision as of 09:18, 25 February 2005
Line 38:		Line 38:

	''FIXME: upload an announcement template for all core GNUstep packages here.''		''FIXME: upload an announcement template for all core GNUstep packages here.''
		+
		+	[[Category:Project procedures]]