Neos 2.3 and Flow 3.3 LTS Release Plan

[dfeyer (Dominique Feyer)]

Neos 2.3 and Flow 3.3 LTS Release Plan

All information related to the upcoming LTS release for Flow and Neos. We need your help to make this first LTS release awesome. The release is planned for end of august, the focus is stability and easing the transition to the next major version More information

[dfeyer (Dominique Feyer)]

This topic is now a banner. It will appear at the top of every page until it is dismissed by the user.

[dfeyer (Dominique Feyer)]

@christianm and me will try to do our best to be the Release Managers with the help of the Unicorns and you.

Goals of the LTS

• Stability (bugfix)
• Prepare upgrade to the next major (namespace, …)
• Better handling of environnement variable (to make it easier to configure Flow in Docker like environnements)

Open PR

At the beginning of @christianm and me spend some time to check all open PR and we create a new tag to flag PR that we think are important for the next LTS:

Flow + Neos

Jira Issue

Check the board Board

Flow + Neos

Open Questions & Discussions

• Next major, PHP7 only ?? Need discussion in the team
• Package naming, namespaces etc. preparation (step 1)

Help wanted

It’s summer and a sunny one, so we need more and more your help, please focus on things needed by the LTS, project related to the next major can start again in September.

Related Posts

Master discussion fixing (package) names

As the next major is coming soon ™ we need to tackle this topic IMHO as waiting another 1.5 years is not helpful. So I want to collect and discuss what is needed and how we tackle it. TYPO3\Flow\Resource\Resource needs to be renamed for future PHP compatibility All TYPO3 package names and namespace need to be renamed to Neos Package names TypoScript, TYPO3CR, Media, Form probably need a rename with our naming policy For Resource a discussion was started in slack with a few ideas already: …

Renaming TypoScript

Continuing the discussion from RFC: Vendor namespace of the Neos Project: -1 for Gluescript, has quite some negative touch for me. But why name it “*script” anyway - one of the major misunderstandings has always been that it’s not a scripting language (or is it?). Now that we have the chance, I’d rather go for something nice and simple, the Neos way. Something like “Swift” (but not Swift of course).

Renaming TYPO3CR

Continuing the discussion from Renaming TypoScript: So does anyone want to bikeshed TYPO3CR? Let’s call it Neos.SolidCR (assuming Neos.TypoScript gets renamed to Neos.Fire).

[kdambekalns (Karsten Dambekalns)]

This topic is no longer a banner. It will no longer appear at the top of every page.