[TYPO3-core] After the LTS is before the LTS
oliver.hader at typo3.org
Thu Jun 26 09:04:52 CEST 2014
Am 25.06.14 14:46, schrieb Martin Sonnenholzer:
> I like the idea of shorter development cycles.
> I agree with the "possible problem" of developers not working with the
> EAR versions, but that seems to be the same problem as with the old in
> between versions. I think this needs a rethinking in the heads of
> developers/ agencies. In my honest opinion this is more of a pro than a
> con, because I like the idea of looking into stable snapshots.
Thanks for your feedback and thoughts, Jigal had quite similar concerns
concerning EAR releases and the actual adoption in the end...
For the development side the shorter phases - instead of 4 months of
features and 2 months of bug fixes, new or missing features can be
merged with the new plan after e.g. some weeks already and makes the
whole process more agile and flexible (for boths, devs and agencies).
The next point is the "always LTS" part which we still need to improve
our automated magic toolboxes a lot concerning upgrade migrations and
checks (the "smooth upgrade thingy" topic). With doing the deprecation
clean-up and the definition on requirements at the beginning of a cycle
(e.g. for "7 LTS"), that branch can be used from the beginning - with
the assumption that all new features are really stable.
We really need to be disciplined about that and reject changes that are
not completely done - like "enhance & try again in four weeks with the
next merge window".
Thus, "flexibility in development and adoption" and "stability" would be
the buzz words for agencies that need to be explained and visualized
much better then.
All the best
TYPO3 CMS Core Team Leader
TYPO3 .... inspiring people to share!
Get involved: http://typo3.org
More information about the TYPO3-team-core