/
Quinnipiac Release Progress

Anuket Project

Quinnipiac Release Progress

Jan 31, 2025

  1.  

    1. M5 (06/02/2025)

      Final documentation completed

      For non specification sub-projects the remaining Jira issues assigned to the release closed or pushed to next release by the PTL-s. Movement of the issues reported to the TSC in a mail or in a TSC meeting.

      There are no non specification sub-projects in the release

      Prepare release artifacts

      PTL-s verify that there are no unmerged patches or PR-s. In case of any unmerged patches or PR-s notify the TSC.

      A volunteer TSC member or LF staff creates release branch for GitHub

      PTL-s create sub-project specific release highlights and report the creation to the TSC
      TSC drafts release announcement blog post and sends it to LF staff for publication

      TSC member finalizes version numbering for the specification projects

      Notes on M5

      M4-S (16/01/2025)

      Proofreading completed
      RA2 is done with the proofreading
       RM is done with the proofreading

      Notes on M4-S

      M4 (08/01/2025)

      Non specification sub-projects have a release branch created by a committer of the sub-project or LF staff

      Specification content created matching high level issues (M2)

      Specification sub-project leads review PR status with TSC

      PRs indicated as closed on the specification dashboard

      Notes on M4

      M3 (SKIPPED)

      For non specification sub-projects participating in the release high priority Jira issues resolved (closed or assigned to future release) last resolved issue is reported to the TSC on mail or in the TSC meeting by the PT

      For non specification sub-projects participating in the release

      preliminary documentation completed (confirmed by volunteer TSC members)

      Notes on M3

      M2 (SKIPPED)

      As there are no software projects participating in this release milestone is skipped

      For non specification sub-projects participating in the release Jira issues assigned to release (should reflect work described in project release plan) by the PTL-s and reported to the TSC in a mail

      High level issues identified by specification sub-project teams and appear on the GitHub dashboard by the PTL-s and reported to the TSC in a mail

    2. Notes on M2

      M1 (28/05/2024)

      Release string "Quinnipiac Release" created in Jira by a volunteer TSC member or LF staff

      Release string "Quinnipiac Release" created in GitHub by a volunteer TSC member or LF staff

      Release milestone dates added to all the GitHub repos by a volunteer TSC member or LF staff

      PTLs of non specification sub-projects submit project-level release plans if they plan to participate in the release

      PTLs of specification sub-projects complete specification planning template for the release

      Notes on M1

      M0 (14/05/2024)

      Release milestones are defined by a volunteer TSC member

      Release milestones approved by the TSC

      Volunteer TSC members sends a mail to the Tech Discuss mailing list asking for PTLs of non specification sub-projects to submit project-level release plans if they plan to participate in the release and asking the PTLs of specification sub-projects to complete the specification planning template for the release

      Notes on M0