... | ... | @@ -29,7 +29,7 @@ Following Stacy's review of the mapped issues, the sign-off criteria are confirm |
|
|
* Evgeny or Martin sign off technical specs for integration-related issues
|
|
|
* Dione confirms the sign-off criteria are complete and sufficiently detailed for the developers to proceed.
|
|
|
|
|
|
In cases where NCBI and Coko teams do not agree on the acceptance criteria, these issues should be floated to the DDWG to resolve together.
|
|
|
In cases where NCBI and Coko teams do not agree on the acceptance criteria, these issues should be floated to the DDWG to resolve together.
|
|
|
|
|
|
### Sign-off issues in-progress
|
|
|
|
... | ... | @@ -39,6 +39,10 @@ These issues can be found on the [Scoping Board](https://gitlab.coko.foundation/ |
|
|
* Sign-off criteria review: issues ready for NCBI review and sign-off
|
|
|
* Sign-off criteria approved: Sign-off responsibility complete
|
|
|
|
|
|
### Change requests and new feature requirements
|
|
|
|
|
|
When changes are requested after the sign-off criteria have been approved, the Gitlab issue should document an estimate of the development time/effort required, as well as any other impacts the changes may have on the schedule. Change requests should only be accepted if they are critical to the priority of Phase 1, namely: the content processing workflow. The same applies to any new feature requests that may arise during Phase 1 development.
|
|
|
|
|
|
## Development workflow
|
|
|
|
|
|
These issues can be found on the [Development Board](https://gitlab.coko.foundation/ncbi/ncbi/-/boards/324)
|
... | ... | @@ -86,6 +90,7 @@ When NCBI has completed testing against the sign-off criteria, Let Dione know in |
|
|
|
|
|
Dione labels each issue as "Dev approved" and closes them.
|
|
|
|
|
|
|
|
|
### Testing agreements
|
|
|
|
|
|
#### For FTP submitted content
|
... | ... | |