...
- Allow ample time for GlastRelease Releases
a GR tag does not imply a validated release- Tags for a new GR need to be submitted a week before the Release is expected to be use in production
- Then a HEAD will be built and submitted to system tests (see below)
- If there is a failure or odd result, the issue should be communicated up to P8 or L1 via JIRA and tracked (see below)
- Repeat as necessary
- Then a HEAD will be built and submitted to system tests (see below)
- Tags for a new GR need to be submitted a week before the Release is expected to be use in production
- Systems Tests
We need more people involved in running and interpreting system test results- A team of 3 or more will be assembled, with a rotating responsibility of running the systems tests.
- People associated P8 and L1 will be involved in validating those results
- Start running system tests on HEADs for P8
Can't offer than up for L1, as we don't have a mechanism to create real HEAD builds in SCons along a branch as we did in CMT- First need to increase our disk allocation
- A team of 3 or more will be assembled, with a rotating responsibility of running the systems tests.
- Windows Support
- More Linux P8 developers plan to make use of glast-ts - begs the question - who is supporting them?
- VC90 requires full Debug externals - while Optimized requires full Opt externals
Certainly seems we only need Debug buildsOptimized builds should be discontinued, and all Windows externals will be provided as full debug with source and distributed via the RM - Issues associated with SCons/GoGui to improve its user friendliness.*** For example, the "clean" needs to really clean so we don't have to go find and delete by hand the "build" folders in each of the subpackages when we make an update to a package
https://jira.slac.stanford.edu/browse/LSC-2 - These and all other issues should be submitted to JIRA (see below)
- SCons RM
Need a better way to deal with failures (especially windows ones)- Unit tests and zip files periodically fail to appear - rerunning those builds from scratch or waiting for the next build is not the best solution
- Document the use of testBuild (run unit tests?) and createReleaseBuild (to recreate zip files on the fly?) or define some other script/exe that we can use as mere humans to populate missing bits in a build
- Define a cron job to automatically reset the permissions on the windows zip files
https://jira.slac.stanford.edu/browse/RM-35
- Unit tests and zip files periodically fail to appear - rerunning those builds from scratch or waiting for the next build is not the best solution
- TMine
- Define Unit tests
- Reintroduce the direct use of TMine into GR, while also maintaining the TMineExt
TMine Developers want access to TMine as a unit independent of GR
However, we need to insure that the same version of ROOT and SConsFiles is used to build TMine in the context of GR
GR can use TMine and its associated packages directly via the packageList.txt, and TMine is no longer an external library.
- Clean Living
- JIRA is our friend
- Random email threads are impossible to track
- New GRs should be requested and tracks via JIRA
- Request comes in with suggested updates for the new release (including tags if possible)
- The request will be tracked in JIRA including updates associated with specific tag requests and system tests results
- SCons Issues including GoGui:
https://jira.slac.stanford.edu/plugins/servlet/project-config/LSC - ReleaseManager (SCons and CMT - as well as RMII web pages)
https://jira.slac.stanford.edu/plugins/servlet/project-config/RM - Pass 8
https://jira.slac.stanford.edu/browse/LPATE - Level 1
https://jira.slac.stanford.edu/browse/LONE
- JIRA is our friend
...