Changes between Version 3 and Version 4 of ReleaseProcedure


Ignore:
Timestamp:
12/15/2009 3:39:01 AM (5 years ago)
Author:
Joel (IP: 220.255.7.118)
Comment:

Add the issue of Symbols and tagging

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v3 v4  
    1111     - Line 7: the version. 
    1212     - Lines 9 onwards: the latest changes. Use svn log to find out. 
     13 3. Commit and changes and tag the builds in SVN so we can go back to it in future (e.g. crash dumps) 
     14 4. Index the PDBs for the Source Server, then use symtool to add the PDBs into the Eraser Symbol Server. 
    1315 
    1416== Build the installer == 
    15  3. The installers are built using Inno (v5) and WiX (v6) 
     17 5. The installers are built using Inno (v5) and WiX (v6) 
    1618   - For v5: Use build/Eraser.iss 
    1719     - Ensure that the binaries inside the installer are signed before packaging them. 
     
    2022 
    2123== Web publish == 
    22  4. This is where betas and stables really differ. 
     24 6. This is where betas and stables really differ. 
    2325   - For betas, upload to the Eraser Web area. Then, update the Eraser database to reflect the release. 
    2426   - For stables, upload to the SourceForge File release system. 
    25  5. Announce in the [http://bbs.heidi.ie/ forum]. 
     27 7. Announce in the [http://bbs.heidi.ie/ forum]. 
    2628   - Always include file hashes. Recommended list: 
    2729     - MD5 
     
    2931     - SHA-256 
    3032     - WHIRLPOOL 
    31  6. Migrate all open tickets to the next version milestone. Also create a new version in Trac for tickets. 
     33 8. Migrate all open tickets to the next version milestone. Also create a new version in Trac for tickets.