move trunk to 6.x, create branch_5x [LUCENE-5944]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
In order to actually add real features (as opposed to just spending 24/7 fixing bugs and back compat), I need a trunk that doesn't have the back compat handcuffs.
In the meantime, we should rename the current trunk (which is totally tied down in back compat already, without even a single release!) to branch_5x while you guys (i wont be doing any back compat anymore) figure out what you want to do with the back compat policly.
Here is the proposal what to do in this issue:
---
Migrated from [LUCENE-5944](https://issues.apache.org/jira/browse/LUCENE-5944) by Robert Muir (@rmuir), updated Sep 19 2014
Contributor guide
Research direction
Start by reading the linked mailing-list proposal and the issue discussion to understand the proposed trunk and branch_5x arrangement. Confirm the branch policy and migration plan with maintainers; done means the agreed branch layout is established without unresolved back-compat decisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100