sijie closed pull request #1112: Update release schedule URL: https://github.com/apache/bookkeeper/pull/1112
This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/site/community/release_guide.md b/site/community/release_guide.md index cded8281d..d7b01d2fe 100644 --- a/site/community/release_guide.md +++ b/site/community/release_guide.md @@ -518,6 +518,13 @@ In JIRA, inside [version management](https://issues.apache.org/jira/plugins/serv In Github, inside [milestones](https://github.com/apache/bookkeeper/milestones), hover over the current milestone and click `close` button to close a milestone and set today's date as due-date. +### Update Release Schedule + +Update the [release schedule](../releases) page (only do this for feature release): + +- Bump the next feature release version and update its release window. +- Update the release schedule to remove released version and add a new release. + ### Checklist to proceed to the next step * Maven artifacts released and indexed in the [Maven Central Repository](https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.bookkeeper%22) @@ -527,6 +534,7 @@ In Github, inside [milestones](https://github.com/apache/bookkeeper/milestones), * Release tagged in the source code repository * Release version finalized in JIRA and Github * Release section with release summary is added in [releases.md](https://github.com/apache/bookkeeper/blob/master/site/releases.md) +* Release schedule page is updated ********** diff --git a/site/community/releases.md b/site/community/releases.md index ac839ec85..1a049bc9c 100644 --- a/site/community/releases.md +++ b/site/community/releases.md @@ -15,19 +15,19 @@ Apache BookKeeper community makes a feture release every 3 month. ### Feature Release Window -The next feature release is `4.6.0`. The release window is the following: +The next feature release is `4.7.0`. The release window is the following: | **Date** | **Event** | -| August 12, 2017 | Merge window opens on master branch | -| October 16, 2017 | Major feature should be in, Cut release branch | -| October 23, 2017 | Minor feature should be in, Stabilize release branch | -| October 30, 2017 - November 12, 2017 | Code freeze, Only accept fixes for blocking issues, Rolling out release candidates | +| November 12, 2017 | Merge window opens on master branch | +| February 12, 2018 | Major feature should be in, Cut release branch | +| February 19, 2018 | Minor feature should be in, Stabilize release branch | +| February 26, 2018 - March 2, 2018 | Code freeze, Only accept fixes for blocking issues, Rolling out release candidates | ## Release Schedule -- **4.6.0**: August 2017 - November 2017 - **4.7.0**: November 2017 - February 2018 - **4.8.0**: Februrary 2018 - May 2018 - **4.9.0**: May 2018 - August 2018 +- **4.10.0**: August 2018 - November 2018 <iframe src="https://calendar.google.com/calendar/embed?src=aam1p2gcoa40n68a6duflnva7c%40group.calendar.google.com&ctz=America/Los_Angeles"; style="border: 0" width="800" height="600" frameborder="0" scrolling="no"></iframe> ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
