Release Life Cycle
Data Access Level
Each different stage of release process will be accessible to different group of audiences, and data access level will differ. (TO DO: Data access levels to be determined by BB).
For each set of data, we need to determine the Data Access Level for a version of SeisFinder.
Example) We have SeisFinder versions 181001 and 181101 and we have just produced Cybershake v18p6 data.
We classify this data as "Internal Only" for SFv181101. This data will not be accessible from SFv181001 regardless of a user class.
Karim (QC staff) will be able to access this data using any release (Trunk, alpha, beta etc) of SFv181101.
However, an early adopter won't be able to access this data set.
When this data set is upgraded to "No Warranty" (after some sanity check), early adopter users will be able to access this data once the SFv181101 beta release is out.
QC Staff
| Release | Data Access Level | ||
| Internal Only | No Warranty | Verified & Validated | |
|---|---|---|---|
| Trunk | O | O | O |
| alpha | O | O | O |
| beta | O | O | O |
| Release Candidate (RC) | O | O | O |
| General Availability (GA) | O | O | O |
Early Adopter
| Release | Data Access Level | ||
| Internal Only | No Warranty | Verified & Validated | |
|---|---|---|---|
| Trunk | X | X | X |
| alpha | X | X | X |
| beta | X | O | O |
| Release Candidate (RC) | X | O | O |
| General Availability (GA) | X | O | O |
Public
| Release | Data Access Level | ||
| Internal Only | No Warranty | Verified & Validated | |
|---|---|---|---|
| Trunk | X | X | X |
| alpha | X | X | X |
| beta | X | X | X |
| Release Candidate (RC) | X | X | X |
| General Availability (GA) | X | X | O |
Users
Three user classes will be used - QC Staff, Early adopters, and Public.
When a user logs in to SeisFinder Web interface, his/her class will be determined and based on it, the data set access will be determined.
Note that only QC Staff will have an access to CLI version of SeisFinder. CLI interface does not need to consider data access control.