Build Package

• Ensure that all library VI dependencies are stated in the package.ogpb (packaging spec) file, including "ogrsc_dynamicpalette >= 0.2", if applicable
• Build Library and Package
• Generate MD5 and put in ./docs/History.txt
• Update ReleaseNotes-x.x.txt with high-level description of changes in ChangeLog-x.x.txt.
• Tag library in SVN
  • Tag URL: https://opengtoolkit.svn.sourceforge.net/svnroot/opengtoolkit/tags/{package_name}/rel-{version_number}
  • Tag Comment: "tagged {package_name}/rel-{version_number}"

Release Package on SourceForge

Upload package file to ftp://upload.sourceforge.net/incoming/

Create a new release of the package on SourceForge

1. Goto http://sourceforge.net/projects/opengtoolkit/
2. Goto Admin >> File Releases
3. Select Add Release for the appropriate package
4. Use package version (e.g., “2.7”) as the New release name
5. Ensure that the correct package is selected for the Of which package pull down menu
6. Select Create This Release (the release will be created and your web browser will be redirected to the Edit Existing Release page, for the release you have just created).

Edit the release and release the package file

1. Ensure that the Release Date, Release Name, Status, and Of Package items are correct, at the top of the page.
2. Upload release notes and change log (set Preserve my pre-formatted text to TRUE/checked)
3. Under Add Files To This Release section, select/check the package file that you uploaded, earlier, and then press the Add Files and/or Refresh View button.
4. Under Edit Files In This Release section, ensure that the correct Filename release is selected. Then set Processor, Release Date, File Type to the appropriate values. Usually Processor is set to “Platform-Independent” and File Type is set to “Other”. Finally, press the Update/Refresh button to accept the new values.
5. Under Email Release Notice section, select/check I’m sure and then press the Send Notice button. This will email people who are subscribed to notifications of new releases.
6. Make note of release ID. This will appear in the SourceForge URL, as a CGI parameter. For example: http://sourceforge.net/project/showfiles.php?group_id=52435&package_id=56149&release_id=468257