These are just some rough notes on the steps needed to make a full release of Jython. I generally run ant full-build as a test beforehand, as well as testing many of these steps throughout, but since that isn't strictly necessary I'm not including it here. full-build requires all of the optional jars for the build be available and named in ant.properties. See build.xml for more information.
- Update files in trunk that have information on the current version
build.xml - <property name="jython.version". Also PY_RELEASE_LEVEL, PY_MICRO_VERSION, PY_MINOR_VERSION and PY_MAJOR_VERSION depending on the level of version bumpage.
- imp.java - If there has been any compiler change, increment magic number APIVersion.
- NEWS
- README
- Run regrtest and the bugtests
- Copy maint to a tag
- build from tag
- set svn.main.dir to tags/Release_2_2_1 in ant.properties
- ant full-build
- upload installer
- go to Admin/File Release on sourceforge
- Click on Add release next to the jython package
- create with a name in line with the version like 2.2rc1
ftp the built installer as on http://sourceforge.net/docman/display_doc.php?docid=6445&group_id=1#upload
- associate the uploaded file with the new release
also update the SourceForge News page (announcement can be added in Admin/News/Submit)
- update files in the website that reference the current release
- constants.txt
- news.txt
- download.txt - checksums
- index.txt - version number
- userfaq.txt - current status
- upload maven package
- ant -Dproject.version=2.2-rc1 in jython/maven
- scp dist/jython-2.2-rc1-bundle.jar shell.sf.net:/home/groups/j/jy/jython/htdocs
File a jira issue for the upload as described in "Posting the request" on http://maven.apache.org/guides/mini/guide-central-repository-upload.html