You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

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
  • Alternatively, a developer could tag Likelihood directly as ScienceTools_v8r3, so that it will be included in ScienceTools_v8r3.

Later discussion revealed a desire for sortable tags.  We finally settled on something like:

v000-000-000, where dashes replace the old "r" and "p".  There were still some murmurs that this convention is a bit long, and some others who missed the "r" and "p".

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.

After we have completely moved to SCons, the old ScienceTools directory could be removed and the ScienceTools-scons could be renamed ScienceTools. 

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. 

Other Concerns

A developer may have ScienceTools in their development area which contains a number of packages, some of which may not be ready for promotion.  Tagging the whole development area will cause those not ready for prime time packages to be tagged as well. 

It was suggested MRStudio could be used to help enforce suitable parameters for tagging. 

We need to discuss with Riccardo about the development path and schedule of MRStudio is. 

Our package structure will fundamentally remain the same, with the eventual elimination of the cmt directories.  CVS updates, checkins, and adds should all function as they do now.

The tag collector will be rewritten.  It will now generate and delete symlinks.  A command line version should also be available.

We briefly discussed the use of subversion rather than CVS. 

  • No labels