Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Since one of the reasons to move off Confluence is to provide online docs for specific versions of Solr, we should agree up front how we'll manage working with the branches.
There are two general proposals on the table so far:
- Make all changes in 'master' (trunk) and backport to branches for
releasing the content. We'd need to merge "backward" into upcoming
release branch. - Make all changes in branch_6x (or branch_7x, etc.) and only move
things to master when they are only applicable to unreleased next
major version. We'd merge 6x "forward" when it's time for next major
version.
Some discussion on this started in the mailing list, so I'll copy the feedback received so far on this as comments to this issue.