Date: Thu, 28 Mar 2024 12:58:01 +0000 (UTC)
Message-ID: <1209529481.11469.1711630681363@aws-us-west-2-edgex-confluence-1.web.codeaurora.org>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_11468_1848628197.1711630681363"
------=_Part_11468_1848628197.1711630681363
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Release Process
Release Process
The EdgeX Release process is outlined and maintained in the foll=
owing documents:
Any references to the release process outside of these two documents may=
be useful in explaining the process but it shouldn't be construed as the p=
oint of record.
Release Process
- Branching
- Normal releases are created off of the
main
bran=
ch. No branches are typically created for a normal release.
- If a bug fix or patch needs to be created to address an existing releas=
e a branch will be created off the tag of the released software version.&nb=
sp;
- During code freeze, only bug and security fixes can now make it into th=
e
main
branch unless truly exceptional. Typically a conversati=
on between WG Chairs, Product Manager and Release Czar is encouraged for aw=
areness.
- Official Release
- An official release is a coordination between the Technical Steering Co=
mmittee (TSC) members, Product Manager, and Release Czar.
- A release schedule is proposed several months before the release date. =
It will include a time for code freeze (typically 2 weeks) and a target dat=
e for the release to occur.
- During Code Freeze the QA/Test working group as well as the Security Wo=
rking group focus on testing and ensuring the release content is ready.
- During or at the end of Code Freeze the TSC members will vote to releas=
e or not.
- The Release Czar will merge a release manifest .yaml file into the CD-Management repository to build/stag=
e/tag and release the desired artifacts. This PR typically gets approved by=
the product manager and relevant TSC members.
- After the release is complete, an announcement will be made by the TSC =
that the
main
branch is open for new contributions and PRs can=
be merged into main
again.
Example Release Checklist=
------=_Part_11468_1848628197.1711630681363--