Changes between Version 21 and Version 22 of WikiStart


Ignore:
Timestamp:
Nov 23, 2010 12:48:56 PM (10 years ago)
Author:
fitz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v21 v22  
    11= BCCD Releases =
    22
    3         The BCCD release schedule is principally based on a "when it's ready" mentality. New versions are released once a bug fixes or features are complete and tested for functionality. While we cannot dictate exactly when new versions will appear, we can define the process by which new releases come about.
     3        The BCCD release schedule is principally based on a "when it's ready" mentality. New versions are released once bug fixes or features are complete and tested for functionality. While we cannot dictate exactly when new versions will appear, we can define the process by which new releases come about.
    44
    5         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 to not 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 every necessary.
     5        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.
    66
    77        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.