Changes between Version 24 and Version 25 of WikiStart


Ignore:
Timestamp:
Jun 18, 2015 7:05:32 PM (4 years ago)
Author:
skylar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v24 v25  
    1111        Each BCCD version number maintains the form X.Y.Z, where X corresponds to significant or fundamental changes, Y corresponds to changes that "add" something, and Z corresponds to changes that "fix" something. Each new version has a corresponding milestone in the BCCD Trac, with which there will be some number of associated tickets. Once all tickets within a milestone are closed a new release will be tagged, a set of ISOs will be generated, and the previous releases will be archived. After being archived, an old build has the potential not to be hosted anymore. That said, the source for every version will still be kept in the repository, making it easy to rebuild an older version if ever necessary.
    1212
    13         Additionally, once a day, a set of ISOs will be generated from the source in trunk at that given moment. These nightly snapshots provide a way for users to play around with the bleeding-edge version of the BCCD and give feedback to the developers on what may or may not be working. Any given nightly snapshot is only available for 24 hours, as it will be overwritten by the subsequent day's build. As such, any bug report must reference the revision number and the day of the build. This information is easily accessible via the command `bccd-version` shipped within the ISOs.
    14 
    1513        It is the Release Engineer's duty to ensure that when a new release is being built, that only those tickets referenced by that version's milestone are being released. In order to enforce this and simultaneously allow active development to continue, a temporary branch will be created for the new version and put under a code freeze while changes are verified and tested. These branches will follow the numbering convention "X.Y.ZrcN" where "rc" is short for "release candidate" and N is an integer standing for which release candidate the branch is. After the release candidate is verified, the release branch and associated builds are created.
    1614