New branches for Neos 2.1 and Flow 3.1 created

Announcements
1

As of a few seconds ago we have new branches for Flow 3.1 and Neos 2.1 - so make sure to target your PRs to the correct branches.

Bugfixes should always be targeted at the lowest supported (and affected) branch, so for now this means probably every bugfix that was/is currently targeted at master should be re-opened for 2.1. Sadly there is no other way… But it’s easy, just checkout the new branch and cherry-pick the needed commits, push to your fork and create a new PR, then close the old (and leave a notice there about the new PR).

For the new branches, no new features must be merged. If in doubt, get in touch with someone from the Minions team.

Any other needed branches (distributions, other packages if needed, …) will be created tomorrow, along with the needed adjustments to build jobs and other tooling.

3 Likes
2

The needed adjustments to the branches have been done now and a few new branches and tags have been created in related packages.

For the development of Neos 2.1, one can now create a project with

composer create-project neos/neos-development-distribution neos-2.1 2.1.x-dev

The Neos base distribution also has a new branch, it can be installed with

composer create-project typo3/neos-base-distribution neos-2.1 2.1.x-dev

Feel free to give this a spin already and report anything unusual…

1 Like
3

For the development of Flow 3.1, one can now create a project with

composer create-project neos/flow-development-distribution flow-3.1 3.1.x-dev

The Flow base distribution also has a new branch, it can be installed with

composer create-project typo3/flow-base-distribution flow-3.1 3.1.x-dev

Feel free to give this a spin already and report anything unusual…

1 Like
4

We now have docs for the new branches at:

And API documentation:

The badges in the Readme.rst file of the collections have been updated as well.

3 Likes