OSG Community Software Testing¶
8 October 2019
The community of OSG resource providers has a vested interest in the quality and stability of the OSG software stack. We would like to notify our stakeholders of software updates as soon as they are designated as "Ready for Testing" by the Software Team. Direct engagement with the entire community would allow for feedback from a broader array of interested parties. Combined with our flexible release model, we hope to further improve the turnaround time of new features and bug fixes.
After the OSG Software Team builds and tests a package successfully, it is marked "Ready for Testing" and is added to the
appropriate Yum testing repository:
osg-upcoming-testing for packages targeted for the release and the upcoming release, respectively.
Upon addition to the relevant testing repository, we intend to notify OSG site administrators that the package, or a
logically connected group of packages, is available for testing with a description of changes compared to previously
released versions and provide a forum by which interested users can provide feedback.
Additionally, any packages that are considered release candidates by their upstream authors will be noted as such.
The Software and Release team will classify packages as either "major" or "minor"; where major packages are deemed critical to the functionality of the production grid and all other packages are minor. For major packages, we will notify site administrators as soon as they are eligible for testing; minor packages eligible for testing will be collected and announced in a weekly digest. After users have been notified of changes, minor packages will be marked eligible for release if they have not received negative feedback after 7 calendar days. In addition to the above requirements, major packages must also receive positive feedback and be approved by the Release Manager. If a package receives negative feedback, the offending package will be removed from the relevant testing repository.
The following packages are considered critical to the production Open Science Grid:
- Frontier Squid
This list is maintained by the Release Manager with input from OSG stakeholders, the Software Manager, and the Operations Manager.
If an expedient release is required, the OSG Software Team may forego the community testing policy outlined above. Common exceptions to the policy include releases that contain one or more of the following:
- Security updates
- CA or VO data updates
- Updates that address installation or upgrade issues
The following email template is filled out to announce that packages are ready for testing. Sections without packages to be tested should be omitted.
Subject: OSG Packages Available for Testing
Several packages are available for testing for tentative release the week of Month Day. OSG 3.5 Only: - Major Components - Major Package n.v.r (Comment, Security, etc.) - Major Package n.v.r - Minor Components - Minor Package n.v.r - Minor Package n.v.r Both OSG 3.5 and 3.4: - Major Components - Major Package n.v.r (Comment, Security, etc.) - Major Package n.v.r - Minor Components - Minor Package n.v.r - Minor Package n.v.r OSG 3.4 Only: - Major Components - Major Package n.v.r (Comment, Security, etc.) - Major Package n.v.r - Minor Components - Minor Package n.v.r - Minor Package n.v.r JIRA Ticket Summary: https://opensciencegrid.atlassian.net/issues/?filter=12355 Please test this software in a non-production environment. Send positive or negative feedback to [email protected] Be sure to include details describing your testing platform: (OSG 3.4 vs 3.5) and (EL6 vs EL7). If you any questions, you can always contact us at [email protected] As described by our Community Software Testing Policy, (https://opensciencegrid.org/technology/policy/community-testing/) Major components of the OSG software stack and need positive feedback and the approval of the release manager before being marked "Ready for Release". Feedback about the community testing process is also desired.
- 2019-10-08: Add policy exceptions
- 2019-08-12: Add notification frequency details
- 2019-02-20: Initial policy