SLAC PEP-II
BABAR
SLAC<->RAL
Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Comp. Search
Who's who?
Meetings
FAQ Homepage
Archive
Environment
Administration
New User Info.
Web Info/Tools
Monitoring
Training
Tools & Utils
Programming
C++ Standard
SRT, AFS, CVS
QA and QC
Remedy
Histogramming
Operations
PromptReco
Simulation Production
Online SW
Dataflow
Detector Control
Evt Processing
Run Control
Calibration
Databases
Offline
Workbook
Coding Standards
Simulation
Reconstruction
Prompt Reco.
BaBar Grid
Data Distribution
Beta & BetaTools
Kanga & Root
Analysis Tools
RooFit Toolkit
Data Management
Data Quality
Event display
Event Browser
Code releases
Databases
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

FAQ Answerpage


QUESTION:
How long is a release kept on disk?


ANSWER:
"Ordinary" releases are kept for 6 weeks:
         > The most recent (re)build in each sequence (i.e. each of the
         > i.j.max(k)) will be kept for 6 weeks.
Releases which have been extensively tested, QA'ed and declared "current" are not "ordinary" and can be retained for longer periods of time. If you feel particular attachment to a release that is being removed, you always have the option of importing that release to your local disk area. However, please keep in mind that release removal is part of the Release Coordinator's responsibility. He/she is asked to remove old releases to (1) stay within a reasonable disk space budget, and (2) keep release management under control.

(Last updated 7/20/98)

[ SLAC Homepage]  [Search] [FAQ Homepage]
If you have a FAQ (with or WITHOUT an answer), use our prototype submission form.
If you have comments or suggestions, email me at sison@slac.stanford.edu