|
|
BESOS releases will be authorized by Paul Kovacs (pkovacs@uvic.ca) along with the help of Ralph Evins (revins@uvic.ca) and Theo Christiaanse (theochri@uvic.ca) who will validate the scientific content.
|
|
|
New additions and features to the code base must pass all current tests in the CI pipeline. In addition to passing current tests, extended functionality must come packaged with tests to validate the extension for future releases. If you have a contribution you would like to make, submit a merge request along with a description of the extended functionality and its intended use. From there the BESOS team will evaluate and validate the code for future releases.
|
|
|
With each major release iteration (x.x.0 or higher), additional functions and classes will be documented in our readthedocs pages and a general overview of the changes can be found in the changelog/release notes.
|
|
|
The BESOS platform intendes to keep up with upgrades and patches of the third-party software implemented within the platform. Upgrades and patches will be implemented on a necessity basis (i.e. known issues and/or features requests could be implemented before non-critical third-party upgrades/patches are applied). |
|
|
\ No newline at end of file |
|
|
The BESOS platform intends to keep up with upgrades and patches of the third-party software implemented within the platform. Upgrades and patches will be implemented on a necessity basis (i.e. known issues and/or features requests could be implemented before non-critical third-party upgrades/patches are applied). |
|
|
\ No newline at end of file |