[
https://issues.apache.org/jira/browse/GEODE-10512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinwoo Hwang updated GEODE-10512:
---------------------------------
Description:
Create the support/2.0 branch from develop for Apache Geode 2.0 release. This
branch will be used to stabilize the release and accept critical fixes before
creating release candidates.
h2. Prerequisites
* LICENSE and NOTICE files have been reviewed and updated on develop
h2. Tasks
h3. 1. Create Support Branch
* Create support/2.0 branch on all projects (geode, geode-examples,
geode-native, geode-benchmarks)
* Update version numbers
* Creating the support pipeline
* Create a PR to bump develop to the next version
h3. 2. Review Benchmark Baseline on Support Branch
Check the benchmark baseline configuration in the support/2.0 branch
h3. 3. Create Pull Request for Develop Bump
h2. Acceptance Criteria
* [ ] support/2.0 branches created on all repositories (geode, geode-examples,
geode-native, geode-benchmarks)
* [ ] Version numbers updated correctly on support/2.0 (2.0.0-build.0)
* [ ] PR for develop version bump created and merged
* [ ] BumpMinor job executed on develop pipeline
* [ ] Community notification email sent to dev list
h2. Branch Protection Rules
Once the support/2.0 branch is created, establish rules for backporting:
* Critical fixes only during stabilization period
* All fixes must go to develop first, then be cherry-picked to support/2.0
* Require PR approval before merging to support/2.0
h2. Notes
* Keep the support branch as stable as possible during the stabilization period
* This is a major release, so breaking changes are acceptable
was:
As part of the Geode 2.0 release preparation, we need to review and update the
LICENSE and NOTICE files to ensure all dependencies and third-party components
are accurately documented before cutting the support branch.
h2. Tasks
h3. 1. License Review Script
Check LICENSE files for:
* Missing dependencies
* Outdated versions
* Dependencies removed since the previous release
h3. 2. Review Dependencies Changes
* Identify any new dependencies added since Geode 1.15.2
* Check if any dependencies were removed and manually verify if stale
references exist in LICENSE or NOTICE files that can be removed
* For new dependencies with Apache 2.0 License, add them to the {{isApache2}}
function in the license_review script
h3. 3. Update Binary Distribution License
If any new 3rd-party .jar files now appear in the binary distribution, update
{{geode-assembly/src/main/dist/LICENSE}} accordingly
h3. 4. Update Source Tree License
If new 3rd-party intellectual property was checked into the source tree (e.g.,
JavaScript libraries, CSS files, etc.), update:
* Root {{LICENSE}} file
* {{geode-assembly/src/main/dist/LICENSE}} file
h3. 5. Review NOTICE File
* Verify all copyright notices are current and accurate
* Ensure all required attributions for third-party components are present
h2. Acceptance Criteria
* All new dependencies are properly documented in LICENSE file(s)
* All removed dependencies have been cleaned up from LICENSE/NOTICE files
* Binary distribution LICENSE is accurate
* Source tree LICENSE includes all checked-in third-party code
* NOTICE file contains all required copyright and attribution notices
* Changes are committed to develop
* Review discussed with community on dev list if any questions arise
h2. Notes
* This should be completed before cutting the support/2.0 branch
* This is a critical step for Apache compliance and release approval
> Create Support Branch for Apache Geode 2.0
> ------------------------------------------
>
> Key: GEODE-10512
> URL: https://issues.apache.org/jira/browse/GEODE-10512
> Project: Geode
> Issue Type: Task
> Reporter: Jinwoo Hwang
> Assignee: Jinwoo Hwang
> Priority: Major
> Fix For: 2.0.0
>
>
> Create the support/2.0 branch from develop for Apache Geode 2.0 release. This
> branch will be used to stabilize the release and accept critical fixes before
> creating release candidates.
> h2. Prerequisites
> * LICENSE and NOTICE files have been reviewed and updated on develop
> h2. Tasks
> h3. 1. Create Support Branch
> * Create support/2.0 branch on all projects (geode, geode-examples,
> geode-native, geode-benchmarks)
> * Update version numbers
> * Creating the support pipeline
> * Create a PR to bump develop to the next version
> h3. 2. Review Benchmark Baseline on Support Branch
> Check the benchmark baseline configuration in the support/2.0 branch
> h3. 3. Create Pull Request for Develop Bump
> h2. Acceptance Criteria
> * [ ] support/2.0 branches created on all repositories (geode,
> geode-examples, geode-native, geode-benchmarks)
> * [ ] Version numbers updated correctly on support/2.0 (2.0.0-build.0)
> * [ ] PR for develop version bump created and merged
> * [ ] BumpMinor job executed on develop pipeline
> * [ ] Community notification email sent to dev list
> h2. Branch Protection Rules
> Once the support/2.0 branch is created, establish rules for backporting:
> * Critical fixes only during stabilization period
> * All fixes must go to develop first, then be cherry-picked to support/2.0
> * Require PR approval before merging to support/2.0
> h2. Notes
> * Keep the support branch as stable as possible during the stabilization
> period
> * This is a major release, so breaking changes are acceptable
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
