Attendees: Joanne Bogart, Toby Burnett, Jim Chiang, Richard Dubois, Navid Golpayegani, Heather Kelly, Eric Winter
After the SCons discussion, we continued on to talk about CVS and checkouts and tagging.
CVS Layout
CVS /
-- ScienceTools
--Likelihood
--flux
--ScienceTools-scons
--Likelihood symlink to original Likelihood above
Suggested Tagging Convention
For a package like Likelihood, rather than tagging as v11, we would not tag as Likelihood_v11
When it comes time to create a new release of ScienceTools, we would do the following:
- Assume the last tag of ScienceTools was ScienceTools_v8r2, and we are now creating ScienceTools_v8r3
- Checkout ScienceTools-scons
- Replace the package(s) you desire to promote, for example replace the version of Likelihood with the "new" version to be included in the new release.
- Now, retag ScienceTools-scons as v8r3
Later discussion revealed a desire for sortable tags. We finally settled on something like:
v000-000-000
Obviously any tagging convention change will impact MRStudio (maybe MRvcmt though many hope MRvcmt is frozen in terms of major change), as well as the workbook.
ReleaseManager Concerns
LATEST builds would remain the same, and would be triggered when a package is tagged. However, Navid suggested we may consider restricting LATEST builds to one, two, or four (TBD) times a day, as well as provide the option for a developer to manually trigger a build. An advantage of the new scheme is that the LATEST "requirements" file is generated by RM - now the "requirements" would be viewable within CVS.
HEAD builds could be triggered by creating a tag named: HEAD-blah
Tagged builds would be triggered just as they are now.