Skip to content

GitHub Projects

aj-agoric edited this page Nov 8, 2024 · 48 revisions

Github Project Fields

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)
Validation Information of how we plan to validate this ticket prior to mainnet deployment. Including info on specific needs such as test nets, oracles, volume transactions etc. Information here will be compiled into an Upgrade validation approach. Required for all tickets needing validation and required prior to being considered code complete.

Dependencies between issues are expressed in a Tasklist named "Dependencies"

Software Release Standard Process (13 Days)

Software Release Standard Process

Phase Days Description
Code Complete 0 date for all work items to be reviewed and closed
Mainnet Clone Testing 3 testing against a network mirroring mainnet with data and infra
Emerynet Announcement 3 opco pledged to announce coming emerynet testing 3 days prior to planned testing(flexible)
Emerynet deploy & Testing 3 validators and opco testing on a shared public test-net for quality and transparency
Mainnet Announcement 3 Opco pledged to announce coming emerynet testing 3 days prior to planned testing
Mainnet Proposal & Voting 3 required 72 open voting period per chain bylaws
Mainnet Upgrade 0 The process of validators performing a coordinated synced upgrade (watchparty)
Mainnet Testing 2 Required testing period for validations of any changes on mainnet
Mainnet Validated 0 all is well, done and done

Github Projects Ticket Phases

Status Description
Open/ Backlog new or unaddressed items which are to be addressed during triage sessions
Ready triaged and placed into the assignee's queue (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
Clone this wiki locally