Changes between Version 1 and Version 2 of ReleaseProcedures
- Timestamp:
- Sep 28, 2008, 7:36:05 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReleaseProcedures
v1 v2 21 21 == Build and privately distribute the Release Package == 22 22 23 The designated builder checks that his source tree is up to date and builds Uniaud32.sys from trunk, Uniaud16.sys, and the installer files. He assembles the zip file based on the file list from the last release, and any changes that were decided. Then sends this in an email to the list of core contributors for review. The designated builder specifies in the message how it was built, and the versions of the tools used, highlighting anything different from previous releases. 24 hours are allowed for responses.23 The designated builder checks that his source tree is up to date and clean, then builds Uniaud32.sys from trunk, Uniaud16.sys, and the installer files. He assembles the zip file based on the file list from the last release, and any changes that were decided. Then sends this in an email to the list of core contributors for review. The designated builder specifies in the message how it was built, and the versions of the tools used, highlighting anything different from previous releases. 24 hours are allowed for responses. 24 24 25 25 This review is important for checking for any mistakes or omissions in the package, last-minute driver tests, and dry-runs of the installer (whose snags frequently are caught at this point). … … 39 39 }}} 40 40 41 == Create Version in Trac == 42 43 The release version, with its release date, is immediately added to Trac in the Admin section, and made the default, so new tickets refer to it. 44 41 45 == Send Announcements == 42 46 … … 46 50 47 51 As soon as practical (ideally at the same time as the release upload, but usually a bit later) the designated builder builds and uploads the debug package to Netlabs. This is Uniaud32 and Uniaud16, built from the same code as the release, but with DEBUG enabled. Like the release, the package contents are based on the previous one, and the Readme.debug is updated as needed. The drivers should be tested by at least one dev first, two if practical. 48 49 == Create Version in Trac ==50 51 The release version, with its release date, is immediately added to Trac in the Admin section, and made the default, so new tickets refer to it.
