Release Instructions - Revision history

LegacyKing: /* Create Release Notes */

2018-11-12T23:54:22Z

‎Create Release Notes

LegacyKing at 23:17, 6 January 2018

2018-01-06T23:17:25Z

LegacyKing: /* The Build */

2017-08-13T05:00:09Z

‎The Build

LegacyKing: /* The Build */

2017-06-17T18:44:59Z

‎The Build

LegacyKing: autobuild

2016-02-03T18:12:08Z

autobuild

LegacyKing: /* The Build */

2016-02-02T09:53:24Z

‎The Build

LegacyKing: Update site pointers

2015-11-05T17:22:28Z

Update site pointers

LegacyKing: /* The Build */

2015-11-05T06:22:13Z

‎The Build

LegacyKing: update to new standards

2015-11-04T18:23:17Z

update to new standards

James at 21:40, 25 May 2015

2015-05-25T21:40:30Z

@@ Line 40: / Line 40: @@
 # Commit the new release notes and notify pcgen_bod so they can review it.
 # Notify pcgen dev and experimental lists of upcoming release, asking for autobuilds to be tested. Best to give 24 hours notice.
 ==The Build==

@@ Line 16: / Line 16: @@
 ===Release===
-* Java SDK 1.7 (the one that includes the javac compiler)
+* Java SDK 1.8 (the one that includes the javac compiler) --FOR PCGEN 6.07.x
 * Gradle 1.x
 * git
@@ Line 88: / Line 88: @@
 Check your versions.
-JDK1.5 is required with JAVA_HOME variable (see below)
+JDK1.8 is required with JAVA_HOME variable (see below)
 SVN must be a true .exe install, TortoiseSVN will not meet this requirement
 SVN exe can be found here [[http://subversion.tigris.org/files/documents/15/46531/Setup-Subversion-1.6.5.msi SVN]]

@@ Line 46: / Line 46: @@
 # Release manager edits '''pcgen/code/src/java/pcgen/resources/prop/PCGenProp.properties''' to set the release date, version number, contributors, etc. and commit the result (5 mins)
 # If switching to or from RC mode, edit '''gradle.properties''' and adjust the version number to be in the correct format. e.g. '''6.04.00 RC1''' or '''6.04.00'''
-# Execute '''gradle prepareRelease slowtest''' in the pcgen directory and verify there are no failing Junit test. Also check if there are any "Unknown publisher" messages. If so you need to add new entries for the listed publishers to the '''gendatalist.pl''' script. (20 mins)
+# Execute '''gradle prepareRelease slowtest''' OR IF USING WINDOWS ('''gradle prepareRelease slowtest --project-cache-dir c:\gradle\cache''')  in the pcgen directory and verify there are no failing Junit test. Also check if there are any "Unknown publisher" messages. If so you need to add new entries for the listed publishers to the '''gendatalist.pl''' script. (20 mins)
 # Check Jira for any closed requests missing from the release notes. Steps 4 and 6 of 'Create Release Notes' section above can be used to assist here. (10 mins)
 # Update the '''readme.md''' file with the what's new section of the release notes.
@@ Line 52: / Line 52: @@
 # Create a folder for the release under the [https://sourceforge.net/projects/pcgen/files/ File Manager]
 # Upload the release notes using the File Manager to the release folder
-# Run '''gradle pcgenRelease''' (which updates the gradlefiles and tags the SVN repository). (2 mins)
+# Run '''gradle pcgenRelease''' OR IF USING WINDOWS ('''gradle pcgenRelease --project-cache-dir c:\gradle\cache''') (which updates the gradlefiles and tags the SVN repository). (2 mins)
 # Upload the release files to SourceForge. The quickest way is uploading via the web, the same way you uploaded the release notes etc. (10 mins)
 # Update '''Readme.MD''' with the SHA256 checksums from target/SHA256-digests.txt. Upload the revised file and check-in. (5 mins)

@@ Line 46: / Line 46: @@
 # Release manager edits '''pcgen/code/src/java/pcgen/resources/prop/PCGenProp.properties''' to set the release date, version number, contributors, etc. and commit the result (5 mins)
 # If switching to or from RC mode, edit '''gradle.properties''' and adjust the version number to be in the correct format. e.g. '''6.04.00 RC1''' or '''6.04.00'''
-# Execute '''gradle clean prepareRelease slowtest''' in the pcgen directory and verify there are no failing Junit test. Also check if there are any "Unknown publisher" messages. If so you need to add new entries for the listed publishers to the '''gendatalist.pl''' script. (20 mins)
+# Execute '''gradle prepareRelease slowtest''' in the pcgen directory and verify there are no failing Junit test. Also check if there are any "Unknown publisher" messages. If so you need to add new entries for the listed publishers to the '''gendatalist.pl''' script. (20 mins)
 # Check Jira for any closed requests missing from the release notes. Steps 4 and 6 of 'Create Release Notes' section above can be used to assist here. (10 mins)
 # Update the '''readme.md''' file with the what's new section of the release notes.
 # Smoke test the newly built pcgen full zip or exe.  (30 mins)
 # Create a folder for the release under the [https://sourceforge.net/projects/pcgen/files/ File Manager]

← Older revision		Revision as of 18:12, 3 February 2016
Line 74:		Line 74:

	See [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/installers/mac-installer/instructions.html Instructions]		See [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/installers/mac-installer/instructions.html Instructions]
		+
		+	==IMPORTANT==
		+	For Production Cycle Autobuilds the file '''code\gradle\autobuild.gradle''' lines 16-18 needs to be set to:
		+	destAutobuildDir = '/home/pcgen1/public_html/autobuilds-prod/'
		+	} else {
		+	destAutobuildDir = "${buildDir}/autobuilds-prod/"
		+

	==Signing Files with PGP==		==Signing Files with PGP==

@@ Line 44: / Line 44: @@
 # Using a clean directory with no changes to the pcgen files
 # '''git pull master''' the PCGen repository (5 mins)
-# Release manager edits pcgen/code/src/java/pcgen/resources/prop/PCGenProp.properties to set the release date, version number, contributors, etc. and commit the result (5 mins)
+# Release manager edits '''pcgen/code/src/java/pcgen/resources/prop/PCGenProp.properties''' to set the release date, version number, contributors, etc. and commit the result (5 mins)
-# If switching to or from RC mode, edit gradle.properties and adjust the version number to be in the correct format. e.g. 6.4.0RC1 or 6.4.0
+# If switching to or from RC mode, edit '''gradle.properties''' and adjust the version number to be in the correct format. e.g. '''6.04.00 RC1''' or '''6.04.00'''
-# Execute '''gradle clean prepareRelease slowtest''' in the pcgen directory and verify there are no failing Junit test. Also check if there are any "Unknown publisher" messages. If so you need to add new entries for the listed publishers to the gendatalist.pl script. (20 mins)
+# Execute '''gradle clean prepareRelease slowtest''' in the pcgen directory and verify there are no failing Junit test. Also check if there are any "Unknown publisher" messages. If so you need to add new entries for the listed publishers to the '''gendatalist.pl''' script. (20 mins)
 # Check Jira for any closed requests missing from the release notes. Steps 4 and 6 of 'Create Release Notes' section above can be used to assist here. (10 mins)
-# Update the readme.md file with the what's new section of the release notes.
+# Update the '''readme.md''' file with the what's new section of the release notes.
 # Execute '''gradle fullZip''' or '''gradle buildNsis''' to generate a testing zip or exe. (3 mins)
 # Smoke test the newly built pcgen full zip or exe.  (30 mins)
@@ Line 55: / Line 55: @@
 # Run '''gradle pcgenRelease''' (which updates the gradlefiles and tags the SVN repository). (2 mins)
 # Upload the release files to SourceForge. The quickest way is uploading via the web, the same way you uploaded the release notes etc. (10 mins)
-# Update Readme.MD with the SHA256 checksums from target/SHA256-digests.txt. Upload the revised file and check-in. (5 mins)
+# Update '''Readme.MD''' with the SHA256 checksums from target/SHA256-digests.txt. Upload the revised file and check-in. (5 mins)
 # Notify PCGen_bod of the new release. (5 mins)
 # PR Monkeys create a news item for the new release

@@ Line 64: / Line 64: @@
 For each of the projects, mark the version you are working on as released and create the next version if it doesn't already exist. When marking a version as released, please make sure the released date is set to today.
-* [http://jira.pcgen.org/plugins/servlet/project-config/CODE/versions Code Versions]
+* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/CODE/versions Code Versions]
-* [http://jira.pcgen.org/plugins/servlet/project-config/DATA/versions Data Versions]
+* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/DATA/versions Data Versions]
-* [http://jira.pcgen.org/plugins/servlet/project-config/DOCS/versions Documentation Versions]
+* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/DOCS/versions Documentation Versions]
-* [http://jira.pcgen.org/plugins/servlet/project-config/NEWSOURCE/versions New Source Versions]
+* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/NEWSOURCE/versions New Source Versions]
-* [http://jira.pcgen.org/plugins/servlet/project-config/NEWTAG/versions New Tag Versions]
+* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/NEWTAG/versions New Tag Versions]
-* [http://jira.pcgen.org/plugins/servlet/project-config/OS/versions Output Sheets Versions]
+* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/OS/versions Output Sheets Versions]
 ==Mac Installer==

@@ Line 31: / Line 31: @@
 ==Create Release Notes==
-# Update your local copy of pcgen from SVN
+# Update your local copy of pcgen from github
 # Copy the previous set of release notes to pcgen-release-notes-nnn.html where nnn is the version number.
 # Do a global replace of the old version number to the new version number, both as n.nn.n and nnnn
@@ Line 37: / Line 37: @@
 # Copy the html to the changelog section, changing h2 tags to h3.
 # Update the What's New section with any high profile changes.
-# Update the Thanks section with the list of people who committed during the cycle.
+# Update the Thanks section with the list of people who committed during the cycle. The search filter "is:pr is:closed is:merged updated:>2015-02-09" is useful for triming the list of pull request to those included in the release.
 # Commit the new release notes and notify pcgen_bod so they can review it.
 # Notify pcgen dev and experimental lists of upcoming release, asking for autobuilds to be tested. Best to give 24 hours notice.