... | @@ -8,7 +8,7 @@ The [Phased Proposal](https://gitlab.coko.foundation/ncbi/ncbi/-/wikis/Project-o |
... | @@ -8,7 +8,7 @@ The [Phased Proposal](https://gitlab.coko.foundation/ncbi/ncbi/-/wikis/Project-o |
|
|
|
|
|
## Use case epics
|
|
## Use case epics
|
|
|
|
|
|
The epic diagrams, provided by NCBI project owner (Stacy) in April 2021 describle NCBI's business uses cases. They include mitigations for a Phase 1 release that excludes supporting users with roles: Data Supplier and Investigator (aka Awardee).
|
|
The epic diagrams, provided by NCBI project owner (Stacy) in April 2021 describe NCBI's business uses cases. They include mitigations for a Phase 1 release that excludes supporting users with roles: Data Supplier and Investigator (aka Awardee).
|
|
|
|
|
|
The epics are organised into four [top-level categories](https://gitlab.coko.foundation/groups/ncbi/-/epics?label_name%5B%5D=top-level+epic):
|
|
The epics are organised into four [top-level categories](https://gitlab.coko.foundation/groups/ncbi/-/epics?label_name%5B%5D=top-level+epic):
|
|
|
|
|
... | @@ -62,14 +62,14 @@ All issues ready for development are on the [Development Board](https://gitlab.c |
... | @@ -62,14 +62,14 @@ All issues ready for development are on the [Development Board](https://gitlab.c |
|
|
|
|
|
Development begins on the issue when the relevant cycle starts (See [Milestone](https://gitlab.coko.foundation/ncbi/ncbi/-/milestones)). Dione may reschedule an issue if the scope changes.
|
|
Development begins on the issue when the relevant cycle starts (See [Milestone](https://gitlab.coko.foundation/ncbi/ncbi/-/milestones)). Dione may reschedule an issue if the scope changes.
|
|
|
|
|
|
The **Development phases**:
|
|
### Development phases:
|
|
|
|
|
|
Issues are added to the Dev board after scope approval and weighting.
|
|
Issues are added to the Dev board after scope approval and weighting. Any issue in the "Dev to do" can be picked up, but the priority are the issues in the the current milestone.
|
|
|
|
|
|
1. Dev to do →
|
|
1. Dev to do →
|
|
2. Dev Doing →
|
|
2. Dev Doing →
|
|
3. Dev Blocked (when relevant) →
|
|
3. Dev Blocked (when relevant) →
|
|
4. Dev QA (assgined to @Sidorelauku) →
|
|
4. Dev QA (assigned to @sidorelauku) →
|
|
5. Dev QA fixes →
|
|
5. Dev QA fixes →
|
|
6. Dev Done →
|
|
6. Dev Done →
|
|
7. Dev Dione QA (check on staging)
|
|
7. Dev Dione QA (check on staging)
|
... | @@ -100,7 +100,7 @@ When NCBI has completed testing against the sign-off criteria, Let Dione know in |
... | @@ -100,7 +100,7 @@ When NCBI has completed testing against the sign-off criteria, Let Dione know in |
|
|
|
|
|
* The current ncbi.coko.foundation will move a new URL managed by our hosting partners to allow daily backups and migrations for each release.
|
|
* The current ncbi.coko.foundation will move a new URL managed by our hosting partners to allow daily backups and migrations for each release.
|
|
* The site will be updated every Tuesday with whichever issues have been completed and merged.
|
|
* The site will be updated every Tuesday with whichever issues have been completed and merged.
|
|
* Dione will proovide release 'walk-thoughs' in the bimonthly review meeting when possible andf will continue to create a summary release issues.
|
|
* Dione will provide release 'walk-throughs' in the bimonthly review meeting when possible and will continue to create a summary release issues.
|
|
|
|
|
|
#### For FTP submitted content
|
|
#### For FTP submitted content
|
|
|
|
|
... | @@ -122,7 +122,4 @@ $ tree /am/ftp-private/bookshelf/coko/mockftp/ |
... | @@ -122,7 +122,4 @@ $ tree /am/ftp-private/bookshelf/coko/mockftp/ |
|
|
|
|
|
1. Coko team will only submit packages to `CADTH` folder. A corresponding Oragnization exists in the BCMS, accessible at Coko's staging site only.
|
|
1. Coko team will only submit packages to `CADTH` folder. A corresponding Oragnization exists in the BCMS, accessible at Coko's staging site only.
|
|
2. NCBI team will submit packages to all other folders. Corresponding Oragnizations exists in the BCMS, accessible at [NCBI's testing site](http://ncbi.coko.foundation) only. These orgs will remain stable in future update of your testing site so you can continue to use them.
|
|
2. NCBI team will submit packages to all other folders. Corresponding Oragnizations exists in the BCMS, accessible at [NCBI's testing site](http://ncbi.coko.foundation) only. These orgs will remain stable in future update of your testing site so you can continue to use them.
|
|
3. Files for testing are maintained is a shared [Nextcloud folder](https://nextcloud.coko.foundation/s/zp26xmB3eP6Px3w) (password protected)
|
|
3. Files for testing are maintained is a shared [Nextcloud folder](https://nextcloud.coko.foundation/s/zp26xmB3eP6Px3w) (password protected) |
|
|
|
\ No newline at end of file |
|
|
|
|
|
|
|
|