|
7 | 7 | The project identified above, which is contained within the repository this |
8 | 8 | document is stored in, has met the following criteria for public release: |
9 | 9 |
|
10 | | -1. [ ] The project, including the test criteria, meets the requirements defined |
| 10 | +1. [x] The project, including the test criteria, meets the requirements defined |
11 | 11 | in the ITS Software Development Publication Policy for making a repository public. |
12 | 12 | The major pre-established criteria for publication are listed below, and the check |
13 | 13 | mark next to each attests that the criterion has been met. |
14 | | - * [ ] Unit tests are available and the software has been tested against the unit tests. |
15 | | - * [ ] The software can be compiled and/or used on Windows, macOS, and Linux. |
16 | | - * [ ] The repository structure and contents follow from the ITS PropLib template, and |
| 14 | + * [x] Unit tests are available and the software has been tested against the unit tests. |
| 15 | + * [x] The software can be compiled and/or used on Windows, macOS, and Linux. |
| 16 | + * [x] The repository structure and contents follow from the ITS PropLib template, and |
17 | 17 | all template or placeholder code has been removed. |
18 | | - * [ ] The repository includes the appropriate `LICENSE.md` file |
19 | | -2. [ ] Any test data necessary for the code and its unit tests to function is included in this |
| 18 | + * [x] The repository includes the appropriate `LICENSE.md` file |
| 19 | +2. [x] Any test data necessary for the code and its unit tests to function is included in this |
20 | 20 | GitHub repository, either directly or as a linked Git submodule. |
21 | | -3. [ ] The README.md file has passed editorial review from the ITS Publications Office. |
22 | | -4. [ ] The project complies with the ITS Code Style Guide or an appropriate style |
| 21 | +3. [x] The README.md file has passed editorial review from the ITS Publications Office. |
| 22 | +4. [x] The project complies with the ITS Code Style Guide or an appropriate style |
23 | 23 | guide as agreed to by the sponsor, project lead, or Supervising Division Chief. |
24 | | -5. [ ] Approved disclaimer and licensing language has been included. |
| 24 | +5. [x] Approved disclaimer and licensing language has been included. |
25 | 25 |
|
26 | 26 | In order to complete this approval, please create a new branch, upload and commit |
27 | 27 | your version of this Markdown document to that branch, then create a pull request |
|
0 commit comments