CcPublisher Release Procedure - Revision history

Sandeep Bhandari: /* Update the Wiki */

2012-02-05T16:51:47Z

‎Update the Wiki

Nathan Yergler: /* Distribute Packages */

2008-09-29T18:21:55Z

‎Distribute Packages

Nathan Yergler at 13:44, 20 June 2006

2006-06-20T13:44:13Z

Nathan Yergler at 00:10, 20 May 2006

2006-05-20T00:10:37Z

Nathan Yergler at 21:04, 19 May 2006

2006-05-19T21:04:09Z

Nathan Yergler at 21:01, 19 May 2006

2006-05-19T21:01:51Z

Nathan Yergler at 17:58, 11 May 2006

2006-05-11T17:58:20Z

Nathan Yergler at 17:35, 11 May 2006

2006-05-11T17:35:35Z

Nathan Yergler at 15:58, 11 May 2006

2006-05-11T15:58:44Z

Nathan Yergler at 19:32, 10 May 2006

2006-05-10T19:32:39Z

@@ Line 90: / Line 90: @@
 == Update the Wiki ==
+[http://www.extreme-java.com Ant Tutorial]
 Create a [[CcPublisher 2 Releases|release page]] and update the latest release on [[CcPublisher]].

@@ Line 87: / Line 87: @@
 == Distribute Packages ==
-Packages are currently distributed from the [http://developer.berlios.de/projects/cctools Berlios project page].  See [[Maximize Software Distribution]] for more distribution information.
+Packages are currently distributed from the [http://developer.berlios.de/projects/cctools Berlios project page].
 == Update the Wiki ==
 Create a [[CcPublisher 2 Releases|release page]] and update the latest release on [[CcPublisher]].

@@ Line 6: / Line 6: @@
 === pyarchive ===
 The <code>pyarchive</code> package is responsible for assembling metadata and uploading files to the [http://archive.org Internet Archive].  The file <code>submission.py</code> contains the version number as part of the uploading application identification.  For example, the current release contains the following code that would need updated for a new release:
@@ Line 29: / Line 31: @@
 === setup.py ===
 <code>setup.py</code> is the primary distutils build script for ccPublisher.  The <code>version</code> parameter passed to the <code>setup</code> function must be updated.

@@ Line 3: / Line 3: @@
 == Increment Version Number ==
-The version number currently needs to be updated in three places.  This will be corrected in the future (see [http://roundup.creativecommons.org/ccpublisher/issue102 Issue 102]).
+The version number currently needs to be updated in four places.  This will be corrected in the future (see [http://roundup.creativecommons.org/ccpublisher/issue102 Issue 102]).
 === pyarchive ===
@@ Line 27: / Line 27: @@
 needs to be updated before the installer is generated.  Note that this '''must''' be a 4 digit version number.
 == Branch or Tag Subversion ==

← Older revision		Revision as of 21:04, 19 May 2006
Line 83:		Line 83:
	== Update the Wiki ==		== Update the Wiki ==

−	Create a release page and update the latest release on [[CcPublisher]].	+	Create a [[CcPublisher 2 Releases\|release page]] and update the latest release on [[CcPublisher]].

@@ Line 72: / Line 72: @@
    $ cd dist
    $ zip -ry ccPublisher-1.9.3.zip ccPublisher.app
 == Distribute Packages ==
 Packages are currently distributed from the [http://developer.berlios.de/projects/cctools Berlios project page].  See [[Maximize Software Distribution]] for more distribution information.

← Older revision		Revision as of 17:58, 11 May 2006
Line 74:		Line 74:

	== Distribute Packages ==		== Distribute Packages ==
		+
		+	Packages are currently distributed from the [http://developer.berlios.de/projects/cctools Berlios project page]. See [[Maximize Software Distribution]] for more distribution information.

← Older revision		Revision as of 17:35, 11 May 2006
Line 30:		Line 30:
	== Branch or Tag Subversion ==		== Branch or Tag Subversion ==

		+	When creating a release, it's important to tag or branch the Subversion repository with version information. In general branches are only for major releases (2.0, etc), while tags are made for each release. You can tag Subversion using a command such as:
		+
		+	$ svn cp svn+ssh://<username>@svn.berlios.de/svnroot/repos/cctools/publisher/trunk svn+ssh://<username>@svn.berlios.de/svnroot/repos/cctools/publisher/tags/ccpublisher-1.9.3
		+
		+	This will create a copy of the current repository trunk as a tag (in the example above for 2.0 beta 3). Note that this only tags changes which have been committed; changes which are in your local sandbox are '''not''' included in the tagged copy.
		+
		+	Branching is performed in a similar fashion.
		+
		+	$ svn cp svn+ssh://<username>@svn.berlios.de/svnroot/repos/cctools/publisher/trunk svn+ssh://<username>@svn.berlios.de/svnroot/repos/cctools/publisher/branches/ccpublisher-2.0

	== Create Packages ==		== Create Packages ==

@@ Line 34: / Line 34: @@
 The package creation process varies slightly for different platforms.  We '''will''' have scripts for this, we just haven't found the right tool.  Ideally something like Ant, but without the Java overhead.  Suggestions welcome.
 === Linux ===
@@ Line 68: / Line 55: @@
 === Mac OS X ===
 == Distribute Packages ==

@@ Line 24: / Line 24: @@
 <code>setup.nsi</code>, located in the deploy/win32 directory of a Subversion checkout, contains instructions for building the installer for Windows.  The version number appears near the top of the file.  The line similar to
-    !define VERSION 1.9.2
+    !define VERSION 1.9.3.0
-needs to be updated before the installer is generated.
+needs to be updated before the installer is generated.  Note that this '''must''' be a 4 digit version number.
 == Branch or Tag Subversion ==
@@ Line 64: / Line 64: @@
 This will assemble the necessary files in the <code>dist</code> subdirectory.  When building ccPublisher, you will see <code>ccpublisher.exe</code>; this is the main application.
-Once the application is built, an installer must be created.  ccPublisher uses [http://nsis.sourceforge.net NSIS] to create Windows installation packages.
+Once the application is built, an installer must be created.  ccPublisher uses [http://nsis.sourceforge.net NSIS] to create Windows installation packages.  The script used to build the installer is deploy/win32/setup.nsi.  If you are using Eclipse, the [http://eclipsensis.soureforge.net EclipseNSIS] plugin allows you to build the installer from within Eclipse.  The [http://nsis.sourceforge.net/Developer_Center NSIS wiki] has documentation on other ways to use NSIS.  After building the installer you'll be left with <code>setup.exe</code> in the working directory (<code>deploy/win32</code> under Eclipse).
 === Mac OS X ===