Transition from a collaborative Git workflow that supports only non-CI testing to one that supports low-cost CI testing and is transparent to community contributors.
As a developer or reviewer, I want to be certain that all code changes pass all merge-request tests.
As a community contributor, I want my contributions to be held to the same standards as the HDF Group’s internal development.
Stage | Description |
---|---|
0 | HDF5 source code is managed in BitBucket. No CI - testing is decoupled from merge requests. Development ad contribution processes are not documented. |
1 | Evaluation of GitHub as a replacement is complete. |
2 | The migration plan is complete and approved. |
3 | GitHub account setup and staff training are completed. |
4 | Repository migration from BitBucket to GitHub is complete. |
5 | The move has been announced to the community and the HDF5 repository is open for contributions. |
6 | Library developer documentation is in place; the GitHub Wiki and issues database are active. |
7 | Improvements to the development and contribution processes are identified and implement. |
8 | The maintenance process for the GitHub repository is in place. |
This card was created by the THG PSIP Pilot project.
This Project Tracking Card originated from the PSIP PTC Catalog. The development of the PSIP PTC Catalog was supported by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of the U.S. Department of Energy Office of Science and the National Nuclear Security Administration.