Go-Live Check-List
The following go-live check-list to help the PMC and respective working group and project leads track progress, including and especially the requirements for activation that must be met to move a release formally to released status.
| Requirement for Activation | Criteria for Release | Explanation | Owner | Status | Comments |
|---|---|---|---|---|---|
| Licensing | |||||
| Project Team | "The project is supported by an engaged project team. While there may not be a formal SLA (depending on the availability of commercial support for the project), bugs and enhancement requests will be triaged and addressed by the team." | From Activation page, "The project should have active contribution from two or more committers." | |||
| Documentation - README.md | "The project is well documented." | README.md requirements met in Github repo | See Documentation Sub-Plan for more detail | ||
| "The project is well documented." | Required and recommended sections of the product (FDC3) microsite | See Documentation Sub-Plan for more detail | |||
| Security | |||||
| Examples | |||||
| Binaries | The installation & upgrade experiences should be relatively smooth - binaries will be available at a minimum, and more advanced deployment options (installers, containers, VM images, automated upgrade scripts etc.) may also be available. | ||||
| Adoption | From Activation page, "Proof of adoption (e.g. in the form of download statistics, citing known deployments, etc.) must be provided." For FDC3, this means there should be a mechanism put in place to track usage and adoption of the standard | ||||
| "The software is functional, though perhaps minimally viable." | Some form of user acceptance testing has been performed. | ||||
| "The software has high quality - it has met or exceeded all of the Foundation's security and compliance requirements, and has been well tested." | Unit, integration, performance, and other forms of testing have been performed an acceptable level of quality achieved. | ||||
| "The installation & upgrade experiences should be relatively smooth - binaries will be available at a minimum, and more advanced deployment options (installers, containers, VM images, automated upgrade scripts etc.) may also be available." | |||||
| "The project is supported by an engaged project team. While there may not be a formal SLA (depending on the availability of commercial support for the project), bugs and enhancement requests will be triaged and addressed by the team. | |||||
| "Backwards compatibility is a priority, and semantic versioning is used to clearly communicate breaking changes." | |||||
Major Tasks, Milestones, and Due Dates
| Milestone | Example Component Tasks | Owner | Deadline | Status | Dependency Notes | Notes |
|---|---|---|---|---|---|---|
| Trademark transferred from OpenFin to FINOS | OpenFin (Nicholas Kolba) and FINOS (Aaron Williamson) | DONE | ||||
| Revised FINOS Branding of FDC3 Delivered |
| FINOS (Tosha Ellison) | IN PROGRESS |
Product release roadmap
Distribution Channels & Launch Activities
| Internal Comms | ||||
| Activity | Owner | Deadline | Status | Links/Notes |
|---|---|---|---|---|
| TO BEGIN | |||
| PR | ||||
| Activity | Owner | Deadline | Status | Links/Notes |
| Activity | Owner | Deadline | Status | Links/Notes |
| Blog | ||||
| Activity | Owner | Deadline | Status | Links/Notes |
| Social | ||||
| Activity | Owner | Deadline | Status | Links/Notes |
Support Plan
Support POC:
| Tasks | Owner | Deadline | Status | Notes |
|---|---|---|---|---|
| TO BEGIN | |||
Reference materials
- Link 1
- Link 2
- Link 3