[ 
https://issues.apache.org/jira/browse/GEODE-10523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jinwoo Hwang updated GEODE-10523:
---------------------------------
    Issue Type: Bug  (was: Task)

> gfsh fails to start with NullPointerException after Spring Shell 3.x migration
> ------------------------------------------------------------------------------
>
>                 Key: GEODE-10523
>                 URL: https://issues.apache.org/jira/browse/GEODE-10523
>             Project: Geode
>          Issue Type: Bug
>            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)

Reply via email to