Changes between Version 17 and Version 18 of ReleasePractices/ManagerCheckList


Ignore:
Timestamp:
Oct 27, 2008, 1:31:51 PM (14 years ago)
Author:
Beman Dawes
Comment:

Add link to ReleasePractices/PostBetaMerges

Legend:

Unmodified
Added
Removed
Modified

  • ReleasePractices/ManagerCheckList

    v17 v18  
    5555    * Monitor the developer and user mailing lists to verify that all posted patches are being applied, rejected, or otherwise dealt with.
    5656       
    57     * Monitor the developer and user mailing lists, and the SourceForge bug tracker, to verify that all posted bug reports are being investigated, fixed, rejected, or otherwise dealt with.
     57    * Monitor the developer and user mailing lists, and outstanding tickets, to verify that all posted bug reports are being investigated, fixed, rejected, or otherwise dealt with.
    5858       
    59     * Monitor CVS commits to verify that all the expected and/or promised content actually gets committed. Try to get developers to avoid last minute commits of major changes.
     59    * Monitor SVN commits to verify that all the expected and/or promised content actually gets committed. Try to get developers to avoid last minute commits of major changes.
     60
     61== Beta Release ==
     62
     63Follow the tagging and release procedures below as for regular releases.
     64
     65== Between Beta and Release ==
     66
     67See ReleasePractices/PostBetaMerges
    6068
    6169== Subversion Release Tag ==