GitHub Projects
| Field | Description |
|---|---|
| Project | The top level initiative or product set example (orchestration API) |
| Component | area within a project (defined feature, product, or effort set delivered to a customer) |
| Release | The planned upgrade or coreEval the item is assigned to |
| Priority | Importance to a release. P1 must ship in the release. P2 is good. P3 should not. P0 trumps all. Engineers should work on the highest priority items in their purview. Priority is driven by a combination of inputs including the upgrade an item is planned for as well as other company needs and dependencies. |
| Effort | The effort needed to complete this item, in number of days expected. Estimated by assignee and their peers. Range 0.5 - 5.0 |
| Delivery Estimate | used in project management to generate reports, forecasted from Effort estimates and backlog (optional, dates for open issues never in the past) |
| Sprint | when a team has committed to deliver it (set in sprint kickoff) |
Dependencies between issues are expressed in a Tasklist named "Dependencies"
| Phase | Days | Description |
|---|
| Code Complete | 0 Days | date for all work items to be reviewed and closed |
| Mainnet Clone Testing | 3 Days | testing against a network mirroring mainnet with data and infra |
| Emerynet Announcement | 3 Days | opco pledged to announce coming emerynet testing 3 days prior to planned testing(flexible) |
| Emerynet deploy & Testing | 3 Days | validators and opco testing on a shared public test-net for quality and transparency |
| Mainnet Announcement | 3 Days | Opco pledged to announce coming emerynet testing 3 days prior to planned testing |
| Mainnet Proposal & Voting | 3 Days | required 72 open voting period per chain bylaws |
| Mainnet Upgrade | 0 Days | The process of validators performing a coordinated synced upgrade (watchparty) |
| Mainnet Testing | 2 Days | Required testing period for validations of any changes on mainnet |
| Mainnet Validated | 0 Days | all is well, done and done |
| Status | Description |
|---|---|
| Open/ Backlog | new or unaddressed items which are to be addressed during triage sessions |
| Up Next | triaged and placed into the assignee's que (assignee) |
| In Progress | Currently being solved by the assignee (assignee) |
| Code Complete | Work done by assignee, needs deployment to chain |
| Releasing | Item has been pulled into a release branch intended for deployment |
| Emerynet Validated | Item has been tested as part of the release branch on Emerynet |
| Mainnet Validated | (done) Item has been tested as part of the release branch on Mainnet |