Das nächste #NeosCMS / #FlowFramework Meetup Hamburg findet am 28. Januar hier bei sitegeist statt!
Themen diesmal:
#OpenAPI -Endpunkte ganz einfach selber bauen mit Sitegeist.SchemeOnYou
Neos 9 in production
#Observability in Flow
Und alles weitere zu Neos und Flow. Außerdem natürlich Pizza und Getränke !
https://www.meetup.com/neos-flow-meetup-hh/events/304629882/
The Neos Team published a new blog post about our Neos 9 Masterplan, which includes out-of-the-row releases of Flow 8.4 and Neos 8.4.
Neos has undergone several major changes during the past 10 years, and the most fundamental one is just on the horizon: Neos 9 - which is all about a new foundation for what lies at the core of the system: Content. How content is stored is a crucial part of our business as a CMS. The old Content Repository (CR) served us well since Neos 1.0, but it has its limits. Therefore, we invested a lot of energy and thought into the new CR which will help us with challenges in the projects of the next 10+ years. Since most of the changes are happening “under the hood”, an editor might not even notice that anything changed at all, whereas integrators and developers might need to adjust to a few changes in the public APIs and get accustomed to the new methods and paradigms.
Merged a bugfix for the @NeosCMS #FlowFramework today that allows properly replacing the integrated CacheFactory.
This in turn allows me to finish implementing a nice feature for the #NeosCMS debug tool that shows the hits/misses/write operations of all caches active during page rendering.
I plan to show hints which caches might need a different configuration or need to be checked whether there are problems with the code based on the amount of calls etc.
https://github.com/neos/flow-development-collection/pull/3318
The previously used method to select the configured CacheFactory class from the Objects.yaml never returned a result as the raw configuration split by package name was accessed, therefore the fallb...
I like the guidelines in Mik Kersten's "Flow framework" for this. It states that deveopers should be working on four things and four things only:
1. Features
2. Defects
3. Risks
4. Tech Debt
The largest percentage will hopefully be new Features, but measuring the ratio of the others could ensure they are not forgotten about (as they often are). Your post is close to this already, I saw.
New updates for the Flow framework are now available for download. These patch level releases include a critical fix that addresses issues that may arise from the recent TYPO3 Fluid update.
https://discuss.neos.io/t/flow-bugfix-releases-7-3-12-8-0-9-8-1-5-8-2-3-8-3-1/6294
I tagged bug fix releases for Neos flow. They fix bugs and inconveniences, as is to be expected. 7.3 and up contain: BUGFIX: Prevent type hint errors with the latest Fluid minor release ChangeLogs: Flow - 7.3.12 ChangeLogs Flow - 8.0.9 ChangeLogs Flow - 8.1.5 ChangeLogs Flow - 8.2.3 ChangeLogs Flow - 8.3.1 ChangeLogs Thanks to those who contributed!
New minor #Neos & #Flow releases were tagged these days: Welcome Neos & Flow 8.1, a.k.a. "Frog-Footman"!
Details and change logs at https://discuss.neos.io/t/neos-flow-8-1-frog-footman-released/6030?u=kdambekalns
Thanks to everyone who contributed, especially @Markus306 for the #NeosUI release!
This Minor Release of Neos and Flow 8.1 “Frog-Footman” is an evolution of the 8.0 release that brings non-breaking changes and features, both visible and under the hood. Read the release blog post on neos.io as well as the upgrade instructions as usual. Here is a list of links to the changes: Neos 8.1.0 Change Log Flow 8.1.0 Change Log Neos Ui 8.1.0 Change Log Enjoy the newest Neos and Flow versions 🙂 Thanks to everyone who contributed code, documentation, translatio...
Please vote and discuss on the important topic. Should #neoscms and #flowframework should go all in with PSR-7 ... I would like to see that and thank Christian for all his efforts.
This is about continuing to move towards fully embracing the PSR-7 HTTP standard. This has relatively far fetching consequences and is rather low level so before I go on with the change I started and invest a lot of time, I wanted to make sure we are on the same page beforehand. We implement PSR-7 interfaces in our HTTP classes but generally do not use any of that, but obviously only if we were to use it fully we can expect some benefit. So we are at a crossroads with this and I am willing to ...
Bernhard Schmitt
Robert Lemke
Mario Rimann
Sebastian Helzle
Tormod Halvorsen
Neos Team
Karsten Dambekalns
Markus