Difference between revisions of "Release Procedures"
Jump to navigation
Jump to search
Jmol/JSmol Development
(added compiling options) |
(Updated other svn links, removed link to changelog and outdated date signature) |
||
| Line 27: | Line 27: | ||
<i>update version number in org/jmol/viewer/JmolConstants.java</i> | <i>update version number in org/jmol/viewer/JmolConstants.java</i> | ||
svn commit -m "prerelease 10.3.1" | svn commit -m "prerelease 10.3.1" | ||
| − | svn copy <nowiki>https://svn.sourceforge.net/svnroot/jmol/trunk</nowiki> \ | + | svn copy <nowiki>https://jmol.svn.sourceforge.net/svnroot/jmol/trunk</nowiki> \ |
| − | <nowiki>https://svn.sourceforge.net/svnroot/jmol/tags/pre10.3.1</nowiki> -m "prerelease 10.3.1" | + | <nowiki>https://jmol.svn.sourceforge.net/svnroot/jmol/tags/pre10.3.1</nowiki> -m "prerelease 10.3.1" |
ant spotless dist | ant spotless dist | ||
cd build/dist | cd build/dist | ||
| Line 61: | Line 61: | ||
=== Inform Jmol users === | === Inform Jmol users === | ||
| − | svn log <nowiki>https://svn.sourceforge.net/svnroot/jmol/trunk</nowiki> | less | + | svn log <nowiki>https://jmol.svn.sourceforge.net/svnroot/jmol/trunk</nowiki> | less |
* Send out a message to [mailto:jmol-users@lists.sourceforge.net jmol-users@lists.sourceforge.net] | * Send out a message to [mailto:jmol-users@lists.sourceforge.net jmol-users@lists.sourceforge.net] | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 20:26, 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
Compiling a Release
Compiling can be done via command line by starting Ant in the top directory, or via an IDE compiler as Eclipse, Netbeans, or JBuilder.
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://jmol.svn.sourceforge.net/svnroot/jmol/trunk \ https://jmol.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://jmol.svn.sourceforge.net/svnroot/jmol/trunk | less
- Send out a message to jmol-users@lists.sourceforge.net
