Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.18.0
-
None
-
None
-
None
Description
The core of the release process is the build-vote-fix cycle. Each cycle produces one release candidate. The Release Manager repeats this cycle until the community approves one release candidate, which is then finalized.
Prerequisites
Set up a few environment variables to simplify Maven commands that follow. This identifies the release candidate being built. Start with RC_NUM equal to 1 and increment it for each candidate:
RC_NUM="1" TAG="release-${RELEASE_VERSION}-rc${RC_NUM}"
Attachments
Issue Links
- blocks
-
FLINK-32920 Finalize release 1.18.0
- Resolved
- is blocked by
-
FLINK-32925 Select executing Release Manager
- Resolved
-
FLINK-32726 [Umbrella] Test Flink Release 1.18
- Resolved
-
FLINK-32921 Prepare Flink 1.18 Release
- Resolved
- is cloned by
-
FLINK-33271 CLONE - Build Release Candidate: 1.18.0-rc2
- Closed
1.
|
Build and stage Java and Python artifacts | Open | Unassigned | |
2.
|
Stage source and binary releases on dist.apache.org | Open | Unassigned | |
3.
|
Propose a pull request for website updates | Open | Unassigned | |
4.
|
Vote on the release candidate | Open | Unassigned |