Changes between Version 11 and Version 12 of pm-svn-releases
- Timestamp:
- Oct 13, 2006 11:50:17 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
pm-svn-releases
v11 v12 40 40 }}} 41 41 42 === Moving Braches === 43 44 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/}}}: 45 46 {{{ 47 svn rm https://projects.coin-or.org/svn/YourProject/trunk \ 48 -m "deleting trunk (so that we can move branches/devel there)" 49 svn mv https://projects.coin-or.org/svn/YourProject/branches/devel \ 50 https://projects.coin-or.org/svn/YourProject/trunk \ 51 -m "moving branches/devel to trunk" 52 }}} 53 42 54 == Working with Stable Versions == 43 55 … … 69 81 === Maintaining a Stable Version === 70 82 71 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.83 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. 72 84 73 85 == Working With Point Releases == 74 86 75 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!'''87 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!''' 76 88 77 89 === 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. 92 104 93 == Creating a Tarball==105 == Tarball Creation == 94 106 95 There's one last step to actually create a tarball for a release: you need to create {{{conf/release.txt}}}. 107 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. 108 109 However, you can use an additional mechanism to create a tarball: You can create {{{conf/release.txt}}}. 96 110 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. 97 111 For example, to create {{{YourProject-2.3.8.tgz}}}, the contents of {{{release.txt}}}