Changes between Version 1 and Version 2 of ReleaseGuidelines


Ignore:
Timestamp:
07/05/10 18:06:55 (10 years ago)
Author:
andrew_b
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseGuidelines

    v1 v2  
    22 
    33While preparing for the release: 
    4  * Create cleanup branch(if needed) with some little patches (usually with typecasts fixies, etc); 
    5  * Create ticket (type=task) for release. Ticket must be blocket by cleanup branch (if present); 
    6  * Update NEWS file into repo and Wiki; 
    7  * New tag in git; 
    8  * New version in Trac; 
    9  * New milestone in trac; 
    10  * Package tar.(gz|bzip|lzma) files and make checksums for archives; 
    11  * Upload source packages and checksums to special upload area; 
    12  * developers must download tarballs, verify checksums, compile and locally install. If all is ok, developers keeps votes in ticket; 
    13  * Upload source packages and checksums to http://www.midnight-commander.org/downloads; 
    14  * Update Wiki start page with latest release number; 
    15  * Write an announcement: list user visible changes (bugs and features); 
    16  * Close current milestone; 
    17  * Close ticket for release. 
    18  
     4 * create cleanup branch (if needed) with some little patches (usually with typecasts fixies, etc); 
     5 * create ticket (type=task) for release. Ticket must be blocked by cleanup branch (if present); 
     6 * update NEWS file in repo and Wiki; 
     7 * new tag in git; 
     8 * new version in Trac; 
     9 * new milestone in Trac; 
     10 * create tar.(gz|bzip|lzma) package files and make checksums for archives; 
     11 * upload source packages and checksums to special upload area; 
     12 * developers must download tarballs, verify checksums, compile and locally install. If everything is ok than developers keep votes in ticket; 
     13 * upload source packages and checksums to http://www.midnight-commander.org/downloads; 
     14 * update Wiki start page with latest release number; 
     15 * write an announcement: list user visible changes (bugs and features); 
     16 * close current milestone; 
     17 * close ticket for release.