| Child pages (Children Display) |
|---|
A few months prior to finalizing a new release of ACME, there will be a scientific "feature freeze" on a specified date.
...
A. After the specified date, no code that introduces new scientific capabilities of the model can be introduced to the version being finalized. More specifically, a
- Steps 1 and 2 of Phase 1 of the /wiki/spaces/CNCL/pages/25231511 must be competed for the feature.
- A github "pull request" for completed code implementing the feature must be made before the feature freeze date/time.
...
- Example: all ACME v1 features must have their coding complete and have a PR issued by 11:59:59 pm PT, .
Q. What if the pull request for my needed feature misses the deadline?
...
A. The integrators need time to bring all the new features to master including new tests and resolve any conflicts . The coupled model team needs time for alpha and beta testing of the model.(Step 3 of Phase 1 of the /wiki/spaces/CNCL/pages/25231511) and the coupled model and performance groups need time to complete their testing/review (Phase 2 of the /wiki/spaces/CNCL/pages/25231511.)
Q. What
...
about alpha and beta
...
versions?
A. See the documentation at Branch, Tag, and Version name conventions.
Q. Can I add code/features
...
for the version being prepared for release before its alpha or beta tags?
A. No. The only changes allowed during the alpha/beta phase are to fix problems with the climate simulations or performance as revealed by alpha/beta test/tuning simulationsPhase 2 of the /wiki/spaces/CNCL/pages/25231511.
Q. What if the feature is completed after the freeze but "turned off" and doesn't change answers and we'd like it in the v1 release?
...
A. Of course if bugs are found in the frozen features during integration testing, fixes for those bugs can go in.
...
A. That is the "code freeze" date and will happen shortly before the release.