GNUstep release procedure
|Revision as of 09:18, 25 February 2005
Stefan Urbanek (Talk | contribs)
← Previous diff
|Revision as of 16:58, 26 February 2005
Tarzeau (Talk | contribs)
Next diff →
|Line 31:||Line 31:|
|''FIXME: add a list in the following form: ''||''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 ==||== Announcement ==|
Revision as of 16:58, 26 February 2005
The release procedure describes steps required to create new release of GNUstep and its packages.
- it should be possible to create a release from clean CVS checkout
- 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.
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.
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 address (it should be a list)
FIXME: upload an announcement template for all core GNUstep packages here.