Changeset 16707

Show
Ignore:
Timestamp:
06/24/08 22:53:28 (3 months ago)
Author:
piotras
Message:

Added few up to date notes.
Removed old ones

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • trunk/midgard/release_howto.txt

    r15571 r16707  
    4646---------------- 
    4747 
    48 * Update local copy of the Midgard CVS repository (example below is for HEAD) 
    49   checkout command (you don't have the repository on your local disk): 
    50     $ cvs -z3 checkout -R midgard 
    51   update command (you have the repository on your local disk already): 
    52     $ cvs -z3 update -dR midgard 
     48* Make sure all sources are up to date and all optional patches  
     49  are ported to particular branch.  
    5350 
    54   (It is always good idea to run makedist from fresh checkouted or updated CVS 
    55   sources, untill makedist absolutely knows what to do.) 
    56  
    57   Do above only when you want to create release from current CVS HEAD branch. 
    58   To make a bugfix release (let's say 1.7.1 and HEAD is for 1.8 development) make branch  
    59   changes: 
    60  
    61      
    62     - checkout (if you don't have the branch repository on local disk): 
    63       * create a new directory (`mkdir cvs-midgard-1-7` for example) 
    64       * cd cvs-midgard-1-7 and cvs checkout according to latest stable branch 
    65         if the branch exists: 
    66           $ cvs -z3 checkout -R -r branch-1-7 midgard 
    67         otherwise: 
    68           $ cvs -z3 checkout -R midgard 
    69  
    70     - update (if you have the branch repository on local disk): 
    71       $ cvs -z3 update -CdR -r branch-1-7 midgard 
    72  
    73     - create the branch: 
    74       * if there is no branch yet for the major version, create it: 
    75         $ cd midgard/src/ && cvs tag -b branch-1-7 
    76  
    77     - make any updates which are required for the new release 
    78       * cd midgard/src/httpd/apache2/ etc. and make updates 
    79       * if a file which should be updated has many revisions since latest stable release 
    80         you may apply changes using '-j' cvs option: 
    81         $ cvs update -j 1.12 -j 1.13 midgard-apache2.c  
    82         (apply changes from 1.13 revision even if release revision was 1.9) 
    83  
    84 * Tag cvs sources with the current release version. 
    85   (for example: cd midgard/src/ && cvs tag release-1-7-1) 
     51* Create new tag for release. 
    8652 
    8753* Run makedist with the version number 
    88   $ ./makedist 1.7.1 
     54  $ ./makedist 2.0.0 
    8955  makedist will also change the version string in midgard-core and 
    9056  copy needed data packages from Midgard website to midgard-data 
    9157 
    9258* Upload packages to http://www.midgard-project.org/download/ 
    93   The article should use the major version (for example 1.7) 
     59  The article should use the major version (for example 2.0) 
    9460  as the URL name 
    9561 
    9662* Ensure that binary packages get generated and uploaded by their 
    9763  maintainers: 
    98   Daniel Reichenbach generates some RPM packages 
    99   Jarkko Ala-Louvesniemi generates Fedora and SuSE RPM packages 
    10064  Piotr Pokora generates Debian packages 
    10165  Jyrki Wahlstedt generates DarwinPorts (OSX) packages 
     66  Binary packages files may be also generated by opensuse build system. 
    10267 
    10368* Add the new version number to Midgard bug tracker configuration 
    10469* Change status of resolved bugs.  
     70 
     71* Do version bump at least in core's configure.in file. 
    10572 
    10673Announcements 
    …… 
    151118 
    152119Also update the entry on Midgard in: 
    153   http://modules.apache.org/search?id=172 
    154120  http://www.macupdate.com/info.php/id/19132 
    155121