Release Procedures - Revision history

Hansonr at 00:23, 28 July 2013

2013-07-28T00:23:08Z

Hansonr: /* Accessing a Release */

2013-07-28T00:18:34Z

‎Accessing a Release

Hansonr: /* Accessing a Release */

2013-07-28T00:16:48Z

‎Accessing a Release

Pimpim: added solution to common sdk compilation problem

2009-06-16T12:48:09Z

added solution to common sdk compilation problem

NicolasVervelle: /* Maintainers only: Release build */ update

2007-12-06T21:46:25Z

‎Maintainers only: Release build: update

NicolasVervelle: /* Maintainers only: release software to sourceforge */ Update

2007-12-06T21:45:19Z

‎Maintainers only: release software to sourceforge: Update

NicolasVervelle: /* Maintainers only: Release build */ update

2007-12-06T21:38:22Z

‎Maintainers only: Release build: update

Pimpim: patches via sourceforge tracker system

2007-08-03T09:15:42Z

patches via sourceforge tracker system

Pimpim at 14:30, 1 August 2007

2007-08-01T14:30:17Z

Pimpim: small intro on svn

2007-08-01T14:21:28Z

small intro on svn

@@ Line 164: / Line 164: @@
   <i>update version number in org/jmol/viewer/Jmol.properties</i>
   svn commit -m "prerelease 10.3.1"
-  svn copy <nowiki>https://jmol.svn.sourceforge.net/svnroot/jmol/trunk</nowiki> \
+  svn copy <nowiki>https://svn.code.sf.net/p/jmol/code/trunk/Jmol</nowiki> \
-     <nowiki>https://jmol.svn.sourceforge.net/svnroot/jmol/tags/pre10.3.1</nowiki> -m "prerelease 10.3.1"
+     <nowiki>https://svn.code.sf.net/p/jmol/tags/pre10.3.1</nowiki> -m "prerelease 10.3.1"
   ant spotless dist
   cd build/dist
@@ Line 200: / Line 200: @@
 === Maintainers only: How to inform Jmol users ===
-  svn log <nowiki>https://jmol.svn.sourceforge.net/svnroot/jmol/trunk</nowiki> | less
+  svn log <nowiki>https://svn.code.sf.net/p/jmol/code/trunk/Jmol</nowiki> | less
 * Send out a message to [mailto:jmol-users@lists.sourceforge.net jmol-users@lists.sourceforge.net]

@@ Line 7: / Line 7: @@
 === 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.
+You can [http://sourceforge.net/p/jmol/code/ browse the latest source code online] or anonymously checkout the project contained in the Subversion (SVN) repository.
 To checkout the Jmol source code use the following command:

@@ Line 9: / Line 9: @@
 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:
+To checkout the Jmol source code use the following command:
-   svn co https://jmol.svn.sourceforge.net/svnroot/jmol/trunk/Jmol
+   svn co https://svn.code.sf.net/p/jmol/code/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 ===

← Older revision		Revision as of 12:48, 16 June 2009
Line 22:		Line 22:

	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.		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.
		+
		+	A common error is:
		+
		+	JmolSVN/Jmol/build.xml:196: Unable to find a javac compiler;
		+	com.sun.tools.javac.Main is not on the classpath.
		+	Perhaps JAVA_HOME does not point to the JDK.
		+	It is currently set to "/usr/lib/jvm/java-1.6.0-openjdk-1.6.0/jre"
		+
		+	To solve this problem, make sure that the (sun) java jdk is installed, and that JAVA_HOME points to its directory, e.g.:
		+
		+	export JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun-1.5.0/
		+
		+	Add this command to your .bashrc if needed.

	=== Editing a Release ===		=== Editing a Release ===

@@ Line 147: / Line 147: @@
   cd incoming
   mput jmol-10.3.1-binary.*
 If you use another ftp client then login with anonymous/emailaddr

@@ Line 162: / Line 162: @@
 ** Create Release
 * Refresh your browser
-* Check {{File|jmol-10.3.1-binary.tar.gz}} and {{File|jmol-10.3.1.binary.zip}}
+* Check {{File|jmol-10.3.1-binary.tar.gz}}, {{File|jmol-10.3.1-binary.zip}} and {{File|jmol-10.3.1-full.tar.gz}}
 * 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: .gz &rarr; Update/Refresh
-* Step 3: Processor: Platform-independent File Type: .zip -> Update/Refresh
+* Step 3: Processor: Platform-independent File Type: .zip &rarr; Update/Refresh
 * Step 4: Email release notes ... check and send
 * At the top of the page click on 'Files'

@@ Line 29: / Line 29: @@
 Hint: Start looking for the source files for the main parts of the program in the 'src/org/jmol' and 'src/org/openscience' subdirectories.
-=== Commiting a bug fix or new feature ===
+=== Submitting a bug fix or new feature patch ===
-Before commiting updated code to the svn server, always do the following:
+Before submitting updated code to the jmol team, always do the following:
 * Test your code thoroughly, try different systems and 'incorrect' input.
 * When the code is working fine, modify the {{File|Jmol.properties}} file in src/org/jmol/viewer. Simply use the same format as the other modifications.
@@ Line 59: / Line 59: @@
 the Jmol.properties file to prepare for the next version.
-Now you are ready to commit, make sure that you are commiting from the top of the Jmol directory tree.
+Now you are ready to submit the changes. For most fixes it will suffice to create a patch file (the file containing the changes compared to a certain revision). Official Jmol maintainers can use the svn commit system.
-The commit message should be short but descriptive.
+Make sure that you are performing the following commands from the top of the Jmol directory tree.
    svn update
    svn status
-   # -- at this point, if conflicts appeared after svn update, solve the conflicts, repeat 'svn status' -- #
+   # At this point, if conflicts appeared after svn update,
    svn diff
    ant spotless dist
    ant test
-It is a good idea to keep the [mailto:jmol-users@lists.sourceforge.net jmol-users@lists.sourceforge.net] mailing list informed of the changes you made.
+As soon as svn status does not present a conflict anymore, your code will be ready to submit.
 ==== SVN Conflicts ====

@@ Line 63: / Line 63: @@
    svn update
-   # -- at this point, if conflicts appeared after svn update, solve the conflicts -- #
+  svn status
    svn diff
    ant spotless dist
@@ Line 73: / Line 74: @@
 ==== SVN Conflicts ====
-'svn update' will check for changes already commited. Possible output is:
+'svn update' will check for changes commited to the server in the time since your last update. Possible output is:
      A  Added
@@ Line 80: / Line 81: @@
      C  Conflict
      G  Merged
 For example:
@@ Line 89: / Line 93: @@
 </pre>
-The conflicting files (marked with a C) need to be checked by hand. Note that 'svn update' will give this warning only once, so do the corrections immediately, or you will forget about them!
+The conflicting files (marked with a C) need to be checked. Note that 'svn update' will give this warning only once, to see if the conflicts have been solved in the mean time, use 'svn status'.
 The conflicting file will contain something like:

← Older revision		Revision as of 14:21, 1 August 2007
Line 1:		Line 1:
	{{Jmol Development Sections}}		{{Jmol Development Sections}}
		+
		+	=== What is this? ===
		+
		+	Several people are working on the Jmol source code at the same time, probably including you! To keep track of the changes and make sure no-one accidentally erases the work done by the other contributors, Jmol uses the subversion (SVN) version control system. These systems are a bit cryptic for the beginning user, therefore an overview of the main procedure is given on this wiki page. General introductions can also be found on the internet, for example a short one [http://www.cs.ubc.ca/~ewout78/SVN.html here], and an on-line book on SVN [http://svnbook.red-bean.com/en/1.1/index.html here] (of the book, the chapter [http://svnbook.red-bean.com/en/1.1/ch03s05.html Basic Work Cycle] gives a good quick start.

	=== Accessing a Release ===		=== Accessing a Release ===