-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d063589
commit b887879
Showing
2 changed files
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
================== | ||
Project Provenance | ||
================== | ||
|
||
Releases are authorized by a committee composed of CHORD and shared platform | ||
software developers and project managers. | ||
|
||
Before publication, release candidates *currently* go through the following | ||
validation process: | ||
|
||
* Comprehensive service- and library-level testing suites | ||
* Testing by hand using synthetic datasets on local machines | ||
* Advance deployment on select instances that opt into testing newer versions | ||
|
||
As part of the release process, documentation is included in the form of tagged | ||
versions of the this website, and service-level ``README`` files for | ||
service-specific technical details. | ||
|
||
The developers of the platform are constantly monitoring for the latest patches | ||
to dependencies used in the project. Any updates that are of critical | ||
importance (bug fixes, security flaws) will warrant a patch release of the | ||
software itself, which will pass through the standard release vetting process. |