Difference between revisions of "Release Procedures"

From Jmol
Jump to navigation Jump to search
(Updated other svn links, removed link to changelog and outdated date signature)
Line 17: Line 17:
 
=== Compiling a Release ===
 
=== Compiling a Release ===
  
Compiling can be done via command line by starting [http://ant.apache.org/ Ant] in the top directory, or via an IDE compiler as [[Eclipse]], [http://www.netbeans.org Netbeans], or [http://www.codegear.com/products/jbuilder JBuilder].
+
Compiling can be done via command line by starting [http://ant.apache.org/ Ant] in the top directory, or via an IDE compiler as [[Eclipse]], [http://www.netbeans.org Netbeans], or [http://www.codegear.com/products/jbuilder JBuilder]. The compiled files will be written to the 'build' subdirectory.
  
 
=== Release build ===
 
=== Release build ===

Revision as of 20:35, 26 July 2007

Jmol/JSmol Development

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. The compiled files will be written to the 'build' subdirectory.

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 File icon.gifjmol-10.3.1-binary.tar.gz and File icon.gifjmol-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