Debian Codegraph @

doc/RELEASE_INSTRUCTIONS

raw
1
2 Things to do before packaging a release
3 ---------------------------------------
4
5 Pre-release:
6 - Do a cvs update -dP and commit all pending changes
7 - Run all unit tests: ./build clean all-tests reports
8 - Run the manual tests in doc/tests/ManualTests.txt
9 - Run the performance tests to see whether performance is about the same
10 (see wiki http://wiki.jboss.org/wiki/Wiki.jsp?page=PerfTests)
11
12
13 Release:
14 - Update the ReleaseNotes-xxx.txt for the given release
15 - Set version in: Version.java, manifest.mf, build.xml and pom.xml
16 * Note that the version needs to conform to the version standards, e.g. 2.6.2.GA or 2.6.4.CR2, 2.5.4.Beta1
17 - Create a CVS tag: JGroups_x_y_z
18 - Add tag information to wiki: http://wiki.jboss.org/wiki/Wiki.jsp?page=Branches
19 - Create a distribution: ./build.sh jar
20 - the distribution files are dist/jgroups-x.y.z.jar, dist/jgroups-sources.jar
21 - Upload distribution files to web site:
22 - Go to http://sourceforge.net/projects/javagroups/
23 - Log in and pick http://sourceforge.net/project/admin/editpackages.php?group_id=6081
24 - Add release to JGroups (new version)
25 - Release notes are included in dist, change log obtained from JIRA
26 - Create PDF and HTML documentation: ./build.sh docs and upload to web site
27 - these files update the JGroups web page (http://www.jgroups.org/javagroupsnew/docs/index.html),
28 specifically the links to manual and tutorial documentation
29 - see JGroups/bin/upload_manual.sh
30 - Create javadoc: ./build.sh javadoc and upload to web site
31 - use process similar to pdf and html (script is bin/upload_javadocs.sh)
32 - Add new release binary jar *and* source jar to Nexus maven repository (http://repository.jboss.org/nexus)
33 a. Run ./bin/release_to_nexus.sh (you need access permissions to Nexus)
34 b. Go to Nexus: https://repository.jboss.org/nexus
35 c. Log in (jboss.org login)
36 d. Click on Staging repositories in the left hand pane
37 e. Right click on the uploaded artifacts (JAR and src JAR) and either drop or promote them. In case of promotion,
38 the artifacts will be promoted to the jboss-releases repository and removed from the staging repo
39 - Announcement to the jg-dev and jg-users mailing lists
40 -include release notes and changelog
41
42
43 NOTE: to perform these steps, you will need a SourceForge account and appropriate
44 permissions.
45