Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
    • M5 (

...

    • 14/

...

    • 05/2023)

      •  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 Pieman,

      •  Prepare release artifacts
        • Tag the version of artifacts to be released
          •  releng job updated to use release branch instead of master

...

        • PTLs collect all artifact references

...

        • and communicates

...

        • them to

...

        • LF staff

...

        • LF staff moves artifacts to hosting location and provides URLs to

...

        • the PTL-s and the TSC
        • PTL-s verify URLs
        • PTL

...

        • provides confirmed URL list to

...

        • LF staff and the TSC for publication on the website

...

        • There are no non specification sub-projects in Pieman
        • 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
          • Beth Cohen started to work on it, but it will be ready only tomorrow
        • TSC member finalizes version numbering for the specification projects

Notes on M5

M4-S (

...

16/

...

04/2023)

  •  Proofreading completed

...

Notes on M4-S

M4 (

...

09/

...

04/2023)

...

  •  

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

    • There are no non specification sub-projects in Pieman
  •  Specification content created matching high level issues (M2)

...

...

Notes on M4

    • There were no changes in RA1, RI1, RC, RI2 and RC2.
    • 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)
        • Volunteer:

      Notes on M3

      M2 (

...

    • skipped)

      •  

...

      • As there are no software projects participating in Pieman 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

        ProjectMail



      •  

        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

        ProjectMail



    • Notes on M2

      M1 (

...

    • 28/

...

    • 11/2023)

...

      •  

...

      • Release string "

...

      • Pieman Release" created in

...

...

...

...

...

    • M0 (24/10/2023)

      •  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


Table of Contents
maxLevel1