Update Release Notes - Revision history

Paul Blankenbaker at 20:04, 6 October 2010

2010-10-06T20:04:53Z

← Older revision		Revision as of 16:04, 6 October 2010
Line 1:		Line 1:
	The release notes at SourceForge will need to be created and or updated. ~~In general,~~ this ~~involves~~ the ~~following:~~		The release notes at SourceForge will need to be created and or updated. This file is generated from the template file: ''include/dist/release-notes.txt''. You should edit/view this file to make sure it looks OK for the current release.

	* Create the file: ~~"''src/sf/sf-release-notes-${VERSION}.html~~''~~" (copy an existing file to use as a starting point).~~		This template file will be used to produce: ''nst-RELEASE/release-notes-RELEASE.txt'' later during the release.

	* Update the information contained in the file (MD5 sums, notes about the release, etc).

	* Upload the release notes to SourceForge.

	* Log into the SourceForge site and go to the file management area. Flag the newly uploaded file as a release notes document.

	* Edit the properties for the other files uploaded for the release and associate them with the release notes document.

	~~Here's example of how one might create and upload the release notes:~~

	~~[root@~~nst-~~dev-32 repo]# cd src~~/sf
	~~[root@nst-dev-32 sf]# cp sf-release-notes-2.11.0.html sf-release-notes-2.12.0.html~~
	~~[root@nst-dev-32 sf]# emacs -nw sf-release-notes-2.12.0.html~~

	~~... Edit release notes HTML ...~~

	~~[root@nst-dev-32 sf]# make release-notes-upload~~

	~~... Output related to the transfer to SourceForge ...~~

	~~[root@nst-dev-32 sf]#~~

	~~= [[Image:Warning.png‎]] Modifying Release Notes =~~

	~~At the time of the 2.11.0 release, it was very difficult to change the release notes file at SourceForge. Here's the process that seemed to work for us:~~

	* Using the SourceForge file manager, remove any associations of other files with the release notes.
	* Using a '''sftp''' connection to SourceForge, remove the existing release notes file.
	* From the NST development box, upload the new version of the release notes document (''make release-notes-~~upload'')~~.
	* Back in the SourceForge file manager rename the '''~~Release Notes~~'~~'' file to a unique name (e.g., '''release-notes-2.11.0-2.html''') that has never been used. Current convention is to increment~~ the ~~subversion number. In this case: "'''-2'''" would become a "'''-3'''".~~
	* Back in the SourceForge file manager set the ''Release Notes'' option under the file properties.
	* Back in the SourceForge file manager associate the new release ~~notes with the other files~~.

Rwh: /* Image:Warning.png‎ Modifying Release Notes */

2009-09-24T10:43:06Z

Image:Warning.png‎ Modifying Release Notes

← Older revision		Revision as of 06:43, 24 September 2009
Line 32:		Line 32:
	* Using a '''sftp''' connection to SourceForge, remove the existing release notes file.		* Using a '''sftp''' connection to SourceForge, remove the existing release notes file.
	* From the NST development box, upload the new version of the release notes document (''make release-notes-upload'').		* From the NST development box, upload the new version of the release notes document (''make release-notes-upload'').
	* Back in the SourceForge file manager rename the '''Release Notes''' file to a unique name (e.g., '''release-notes-2.11.0-2.html''') that has never been used. Current convention is to increment the subversion number. In ~~the~~ case: "'''-2'''" would become a "'''-3'''".		* Back in the SourceForge file manager rename the '''Release Notes''' file to a unique name (e.g., '''release-notes-2.11.0-2.html''') that has never been used. Current convention is to increment the subversion number. In this case: "'''-2'''" would become a "'''-3'''".
	* Back in the SourceForge file manager set the ''Release Notes'' option under the file properties.		* Back in the SourceForge file manager set the ''Release Notes'' option under the file properties.
	* Back in the SourceForge file manager associate the new release notes with the other files.		* Back in the SourceForge file manager associate the new release notes with the other files.

Rwh: /* Image:Warning.png‎ Modifying Release Notes */

2009-09-24T10:42:32Z

Image:Warning.png‎ Modifying Release Notes

← Older revision		Revision as of 06:42, 24 September 2009
Line 32:		Line 32:
	* Using a '''sftp''' connection to SourceForge, remove the existing release notes file.		* Using a '''sftp''' connection to SourceForge, remove the existing release notes file.
	* From the NST development box, upload the new version of the release notes document (''make release-notes-upload'').		* From the NST development box, upload the new version of the release notes document (''make release-notes-upload'').
	* Back in the SourceForge file manager rename the ''Release Notes'' to a unique name (e.g., release-notes-2.11.0-2.html) that has never been used. Current convention is to increment the subversion number. In the case: "'''-2'''" would become a "'''-3'''".		* Back in the SourceForge file manager rename the '''Release Notes''' file to a unique name (e.g., '''release-notes-2.11.0-2.html''') that has never been used. Current convention is to increment the subversion number. In the case: "'''-2'''" would become a "'''-3'''".
	* Back in the SourceForge file manager set the ''Release Notes'' option under the file properties.		* Back in the SourceForge file manager set the ''Release Notes'' option under the file properties.
	* Back in the SourceForge file manager associate the new release notes with the other files.		* Back in the SourceForge file manager associate the new release notes with the other files.

Rwh: /* Image:Warning.png‎ Modifying Release Notes */

2009-09-24T10:41:40Z

Image:Warning.png‎ Modifying Release Notes

← Older revision		Revision as of 06:41, 24 September 2009
Line 32:		Line 32:
	* Using a '''sftp''' connection to SourceForge, remove the existing release notes file.		* Using a '''sftp''' connection to SourceForge, remove the existing release notes file.
	* From the NST development box, upload the new version of the release notes document (''make release-notes-upload'').		* From the NST development box, upload the new version of the release notes document (''make release-notes-upload'').
			* Back in the SourceForge file manager rename the ''Release Notes'' to a unique name (e.g., release-notes-2.11.0-2.html) that has never been used. Current convention is to increment the subversion number. In the case: "'''-2'''" would become a "'''-3'''".
	* Back in the SourceForge file manager set the ''Release Notes'' option under the file properties.		* Back in the SourceForge file manager set the ''Release Notes'' option under the file properties.
	* Back in the SourceForge file manager associate the new release notes with the other files.		* Back in the SourceForge file manager associate the new release notes with the other files.

Rwh: /* Modifying Release Notes */

2009-09-24T10:35:44Z

Modifying Release Notes

← Older revision		Revision as of 06:35, 24 September 2009
Line 25:		Line 25:
	[root@nst-dev-32 sf]#		[root@nst-dev-32 sf]#

	= Modifying Release Notes =		= [[Image:Warning.png‎]] Modifying Release Notes =

	At the time of the 2.11.0 release, it was very difficult to change the release notes file at SourceForge. Here's the process that seemed to work for us:		At the time of the 2.11.0 release, it was very difficult to change the release notes file at SourceForge. Here's the process that seemed to work for us:

Paul Blankenbaker at 01:07, 24 September 2009

2009-09-24T01:07:01Z

← Older revision		Revision as of 21:07, 23 September 2009
Line 24:		Line 24:

	[root@nst-dev-32 sf]#		[root@nst-dev-32 sf]#

			= Modifying Release Notes =

			At the time of the 2.11.0 release, it was very difficult to change the release notes file at SourceForge. Here's the process that seemed to work for us:

			* Using the SourceForge file manager, remove any associations of other files with the release notes.
			* Using a '''sftp''' connection to SourceForge, remove the existing release notes file.
			* From the NST development box, upload the new version of the release notes document (''make release-notes-upload'').
			* Back in the SourceForge file manager set the ''Release Notes'' option under the file properties.
			* Back in the SourceForge file manager associate the new release notes with the other files.

Paul Blankenbaker: New page: The release notes at SourceForge will need to be created and or updated. In general, this involves the following: * Create the file: "''src/sf/sf-release-notes-${VERSION}.html''" (copy an...

2009-09-23T11:33:28Z

New page: The release notes at SourceForge will need to be created and or updated. In general, this involves the following: * Create the file: "''src/sf/sf-release-notes-${VERSION}.html''" (copy an...

New page

The release notes at SourceForge will need to be created and or updated. In general, this involves the following:

* Create the file: "''src/sf/sf-release-notes-${VERSION}.html''" (copy an existing file to use as a starting point).

* Update the information contained in the file (MD5 sums, notes about the release, etc).

* Upload the release notes to SourceForge.

* Log into the SourceForge site and go to the file management area. Flag the newly uploaded file as a release notes document.

* Edit the properties for the other files uploaded for the release and associate them with the release notes document.

Here's example of how one might create and upload the release notes:

[root@nst-dev-32 repo]# cd src/sf
[root@nst-dev-32 sf]# cp sf-release-notes-2.11.0.html sf-release-notes-2.12.0.html
[root@nst-dev-32 sf]# emacs -nw sf-release-notes-2.12.0.html

... Edit release notes HTML ...

[root@nst-dev-32 sf]# make release-notes-upload

... Output related to the transfer to SourceForge ...

[root@nst-dev-32 sf]#