Changes between Version 14 and Version 15 of pm-svn-releases


Ignore:
Timestamp:
Oct 18, 2006 1:09:23 AM (14 years ago)
Author:
andreasw
Comment:

added link to externals point release checklist, and replaced tarball section to pm-svn-conf

Legend:

Unmodified
Added
Removed
Modified
  • pm-svn-releases

    v14 v15  
    9191Typically, you would have a version of your code in a stable branch, say {{{stable/2.3/}}}, which you now want to make an official release.  '''Remember, it is mandatory that one can recreate exactly the same version in the future''', ''i.e.'', you should not change anything in a point release after you set it up.
    9292
    93 '''If you are using [wiki:pm-svn-externals Externals]''':  Before creating the new release from the current version in the stable branch, '''you need to make sure that all {{{svn:externals}}}, in the version that you want to make the release, are pointing to ''releases'' of the dependencies''' so that your release can be recreated exactly at any point in time, independent of continuing development of the dependencies.  Please make sure that all URLs in your {{{Externals}}} file are pointing to something in the {{{release}}} directory of each dependency.  Also, make sure that the {{{svn:externals}}} property is indeed set according to the file content (verify with, ''e.g.'', {{{svn pget svn:externals https://projects.coin-or.org/svn/YourProject/stable/2.3}}}).  (Note: If for some reason a compatible release for a dependency does not exist, you must specify the subversion revision number, using the "{{{-r}}}" flag in the {{{externals}}} definition.)  Please read [wiki:pm-svn-externals here] for additional explanation of how to handle externals in COIN.
     93'''If you are using [wiki:pm-svn-externals Externals]''':  Before creating the new release from the current version in the stable branch, '''you need to make sure that all {{{svn:externals}}}, in the version that you want to make the release, are pointing to ''releases'' of the dependencies''' so that your release can be recreated exactly at any point in time, independent of continuing development of the dependencies.  Please make sure that all URLs in your {{{Externals}}} file are pointing to something in the {{{release}}} directory of each dependency.  Also, make sure that the {{{svn:externals}}} property is indeed set according to the file content (verify with, ''e.g.'', {{{svn pget svn:externals https://projects.coin-or.org/svn/YourProject/stable/2.3}}}).  (Note: If for some reason a compatible release for a dependency does not exist, you must specify the subversion revision number, using the "{{{-r}}}" flag in the {{{externals}}} definition.)  '''Please use the [wiki:pm-svn-externals#PreparingExternalsForAPointReleaseexternals checklist] to make sure things work properly.'''
    9494
    9595To create a new release, say 2.3.8, you use the {{{svn copy}}} command:
     
    105105== Tarball Creation ==
    106106
    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 use a file, {{{conf/release.txt}}}.
    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.
    111 For example, to create {{{YourProject-2.3.8.tgz}}}, the contents of {{{release.txt}}}
    112 would be
    113 {{{
    114 releases/2.3.8    2.3.8
    115 }}}
    116 
    117 To create this file, use {{{svn add}}} and {{{svn commit}}} to add it to the
    118 {{{conf/}}} directory. The commit will take a loooong time, because the tarball is created on the spot. When the commit finishes, your tarball will be ready in the COIN downloads directory. Subsequently, after you've created a new point release in {{{releases/}}, simply edit and commit {{{releases.txt} to trigger the creation of a new tarball.
     107For information on the automatic tarball creation look [wiki:pm-svn-conf here].