Versions Compared

Old Version 75

changes.mady.by.user Gwen Shapira

Saved on

compared with

New Version 76

changes.mady.by.user Gwen Shapira

Saved on

Key

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

...

  • Prepare release plan in the wiki, notifying the community the overall plan and goals for the release (For example: Release Plan 0.10.0)

  • Vote on release plan: Release manager should start a vote in dev@kafka.apache.org, asking the community to approve the release plan. 

    No Format
    To: dev@kafka.apache.org
Subject: [VOTE] Release plan - Kafka 0.10.0

We are starting the process to prepare for Kafka $release release. I have created release plan ($link) to cover the tasks under this release.

If you have any JIRA in progress and would like to include it in this release, please follow the process to do so.

Feel free to comment on the JIRA if you have any comments/suggestions.

Thanks,
$RM

  • Go over JIRA for the release and make sure that blockers are marked as blockers and non-blockers are non-blockers. This JIRA filter may be handy:

    No Format
    project = KAFKA AND fixVersion = 0.10.0.0 AND resolution = Unresolved AND priority = blocker ORDER BY due ASC, priority DESC, created ASC

  • It is important that between the time that the release plan is voted to the time when the release branch is created, no experimental or potentially destabilizing work is checked into the trunk. While it is acceptable to introduce major changes, they must be thoroughly reviewed and have good test coverage to ensure that the release branch does not start of being unstable. If necessary the RM can discuss if certain issues should be fixed on the trunk in this time, and if so what is the gating criteria for accepting them.

...