Difference between revisions of "Release Procedures"
Jump to navigation
Jump to search
Jmol/JSmol Development
(Added jmol development sections template) |
|||
Line 1: | Line 1: | ||
{{Jmol Development Sections}} | {{Jmol Development Sections}} | ||
+ | |||
+ | === Accessing a Release === | ||
+ | |||
+ | You can [http://jmol.svn.sourceforge.net/viewvc/jmol/ browse the latest source code online] or anonymously checkout the project contained in the Subversion (SVN) repository. | ||
+ | |||
+ | To checkout the source code use the following command: | ||
+ | |||
+ | svn co https://jmol.svn.sourceforge.net/svnroot/jmol/trunk/Jmol | ||
+ | |||
+ | This will check out to the Jmol subdirectory on your system. | ||
+ | |||
+ | You can update the source code from withing your Jmol sandbox by saying: | ||
+ | |||
+ | svn update | ||
+ | |||
+ | |||
=== Release build === | === Release build === | ||
Revision as of 19:38, 26 July 2007
- Getting Involved in J(S)mol evolution
- Release Procedures
- Important! Use the Jmol Coding Style
- Developing J(S)mol with Eclipse
- Internationalisation (status)
- ProgrammeerZomer / SummerOfCode
- MultiUser Jmol
- Developer mailing list (mirror)
Contents
Accessing a Release
You can browse the latest source code online or anonymously checkout the project contained in the Subversion (SVN) repository.
To checkout the source code use the following command:
svn co https://jmol.svn.sourceforge.net/svnroot/jmol/trunk/Jmol
This will check out to the Jmol subdirectory on your system.
You can update the source code from withing your Jmol sandbox by saying:
svn update
Release build
svn update ant spotless dist ant test update version number in build.xml update version number in org/jmol/viewer/JmolConstants.java svn commit -m "prerelease 10.3.1" svn copy https://svn.sourceforge.net/svnroot/jmol/trunk \ https://svn.sourceforge.net/svnroot/jmol/tags/pre10.3.1 -m "prerelease 10.3.1" ant spotless dist cd build/dist ls lftp upload.sourceforge.net cd incoming mput jmol-10.3.1-binary.*
If you use another ftp client then login with anonymous/emailaddr and put ftp into 'bin' mode to ensure clean transfer of binary files.
To release software to sourceforge
From http://sourceforge.net/projects/jmol :
- Admin
- File Releases
- in File Release Packages:
- Edit Releases in order to look at previous release name conventions
- Add Release - prerelease 10.3.1
- Type in name
- Create Release
- Refresh your browser
- Check jmol-10.3.1-binary.tar.gz and jmol-10.3.1.binary.zip
- Add Files and/or Refresh View
- Scroll down to Step 3: Edit files in this release
- Step 3: Processor: Platform-independent File Type: .gz Update/Refresh
- Step 3: Processor: Platform-independent File Type: .zip -> Update/Refresh
- Step 4: Email release notes ... check and send
- At the top of the page click on 'Files'
- If you want, edit older releases and change them from Active to Hidden
Inform Jmol users
svn log https://svn.sourceforge.net/svnroot/jmol/trunk | less
- Send out a message to jmol-users@lists.sourceforge.net
- Update the Change Log page.
Miguel 2006 04 04