977
Comment:
|
2339
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
These are just some rough notes on the steps I take to release Jython. | 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. |
Line 3: | Line 3: |
1. Version bumps 1. PySystemState.java 1. build.xml 1. NEWS 1. README 1. Tag release 1. make svn tag dir 1. svn cp trunk/jython into tag dir 1. svn cp trunk/installer into tag dir 1. build from tag 1. svn co tag 1. cp ant.properties into release checkout/jython 1. ant full-build in release checkout/jython 1. upload build 1. go to Admin/File Release on sourceforge 1. Click on Add release next to the jython package 1. create with a name in line with the version like 2.2rc1 1. ftp the built installer as on http://sourceforge.net/docman/display_doc.php?docid=6445&group_id=1#upload 1. associate the uploaded file with the new release 1. update site 1. news.txt 1. download.txt 1. index.txt 1. installation.txt 1. userfaq.txt 1. upload maven package 1. ant -Dproject.version=2.2-rc1 in jython/maven 1. scp dist/jython-2.2-rc1-bundle.jar shell.sf.net:/ |
1. Update files in trunk that have information on the current version 1. PySystemState.java - version and PY_RELEASE_SERIAL at least. Also PY_RELEASE_LEVEL, PY_MICRO_VERSION, PY_MINOR_VERSION and PY_MAJOR_VERSION depending on the level of version bumpage. 1. build.xml - <property name="svn.tag", <property name="jython.version", and make values in <target name="version" match PySystemState. 1. NEWS 1. README 1. Copy trunk and installer to a tag 1. svn mkdir https://jython.svn.sourceforge.net/svnroot/jython/tags/Release_2_2rc2 1. svn cp https://jython.svn.sourceforge.net/svnroot/jython/trunk/jython https://jython.svn.sourceforge.net/svnroot/jython/tags/Release_2_2rc2 1. svn cp https://jython.svn.sourceforge.net/svnroot/jython/trunk/installer https://jython.svn.sourceforge.net/svnroot/jython/tags/Release_2_2rc2 1. build from tag 1. svn co tag release_checkout 1. cp ant.properties into release_checkout/jython 1. ant full-build in release_checkout/jython 1. upload installer 1. go to Admin/File Release on sourceforge 1. Click on Add release next to the jython package 1. create with a name in line with the version like 2.2rc1 1. ftp the built installer as on http://sourceforge.net/docman/display_doc.php?docid=6445&group_id=1#upload 1. associate the uploaded file with the new release 1. update files in the website that reference the current release 1. news.txt 1. download.txt 1. index.txt - version number and download location 1. installation.txt - installer file name, download location 1. userfaq.txt - current status, download link 1. upload maven package 1. ant -Dproject.version=2.2-rc1 in jython/maven 1. scp dist/jython-2.2-rc1-bundle.jar shell.sf.net:/home/groups/j/jy/jython/htdocs 1. 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 |
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
PySystemState.java - version and PY_RELEASE_SERIAL at least. Also PY_RELEASE_LEVEL, PY_MICRO_VERSION, PY_MINOR_VERSION and PY_MAJOR_VERSION depending on the level of version bumpage.
build.xml - <property name="svn.tag", <property name="jython.version", and make values in <target name="version" match PySystemState.
- NEWS
- README
- Copy trunk and installer to a tag
svn mkdir https://jython.svn.sourceforge.net/svnroot/jython/tags/Release_2_2rc2
svn cp https://jython.svn.sourceforge.net/svnroot/jython/trunk/jython https://jython.svn.sourceforge.net/svnroot/jython/tags/Release_2_2rc2
svn cp https://jython.svn.sourceforge.net/svnroot/jython/trunk/installer https://jython.svn.sourceforge.net/svnroot/jython/tags/Release_2_2rc2
- build from tag
- svn co tag release_checkout
- cp ant.properties into release_checkout/jython
- ant full-build in release_checkout/jython
- 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
- update files in the website that reference the current release
- news.txt
- download.txt
- index.txt - version number and download location
- installation.txt - installer file name, download location
- userfaq.txt - current status, download link
- 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