Changes between Version 11 and Version 12 of pm-svn-releases

Timestamp:

Oct 13, 2006 11:50:17 PM (13 years ago)

Author:

andreasw

Comment:

add instructions on how to move branches/devel to trunk; explain that tarball creation is done by default automatically

pm-svn-releases

@@ -40 +40 @@
 }}}
 
+=== Moving Braches ===
+
+Some of the existing COIN projects had a development branch {{{branches/devel/}}}.  With the transition to the new release policy described here, this branch should now become {{{trunk/}}}.  The easiest way to do this, is to first delete the old {{{trunk/}}} directory in the subversion repository (assuming that the previous "stable release" content has been copied into an appropriate place in {{{stable/}}} and/or {{{releases/}}}), and then to move {{{branches/devel/}}} to {{{trunk/}}}:
+
+{{{
+svn rm https://projects.coin-or.org/svn/YourProject/trunk \
+           -m "deleting trunk (so that we can move branches/devel there)"
+svn mv https://projects.coin-or.org/svn/YourProject/branches/devel \
+           https://projects.coin-or.org/svn/YourProject/trunk \
+           -m "moving branches/devel to trunk"
+}}}
+
 == Working with Stable Versions ==
 
@@ -69 +81 @@
 === Maintaining a Stable Version ===
 
-To change the content of a stable version, you work with it as usual: creating (checking out) a local copy of the code in that branch, making changes there (directly by editing, or by using {{{svn merge}}} to include changes made in a different version in the repository, such as {{{trunk}}}), and finally submitting the changes back to the repository.
+To change the content of a stable version, you work with it as usual: creating (checking out) a local copy of the code in that branch, making changes there (directly by editing, or [wiki:pm-svn-branches by using {{{svn merge}}}] to include changes made in a different version in the repository, such as {{{trunk}}}), and finally submitting the changes back to the repository.
 
 == Working With Point Releases ==
 
-The {{{release}}} directory is the place where a user can find particular, numbered releases.  The tarballs distributed on the COIN-OR website are created from these releases.  It is mandatory that checking out a release from this place in the repository always provides the identical code, so that it's possible to restore older versions (''e.g.'', to reproduce a bug reported by a user).  In this context you need to be careful if you use {{{svn:externals}}}.  '''Once a release has been created it must not be changed!'''
+The {{{releases/}}} directory is the place where a user can find particular, numbered releases.  The tarballs distributed on the COIN-OR website are created from these releases.  It is mandatory that checking out a release from this place in the repository always provides the identical code, so that it's possible to restore older versions (''e.g.'', to reproduce a bug reported by a user).  In this context you need to be careful if you use {{{svn:externals}}}.  '''Once a release has been created it must not be changed!'''
 
 === Creating a New Point Release ===
@@ -91 +103 @@
 Again, it is a very good idea to log the subversion repository revision number in the commit message.
 
-== Creating a Tarball ==
+== Tarball Creation ==
 
-There's one last step to actually create a tarball for a release: you need to create {{{conf/release.txt}}}.
+Unless you instructed the COIN-OR website maintainer otherwise, tarballs for your project will be created automatically every night for each point release in your {{{releases/}}} directory.
+
+However, you can use an additional mechanism to create a tarball: You can create {{{conf/release.txt}}}.
 The contents of {{{release.txt}}} should be a single line specifying the root of the release directory in the repository, and the version number used for the tarball.
 For example, to create {{{YourProject-2.3.8.tgz}}}, the contents of {{{release.txt}}}