Blog

During our latest sprint in Dresden we looked back at the last months and decided to adjust the way we want to work with teams and projects in the Neos community. This post explains the changes…

A solid release plan and strategy is important for developers, customers and users. It increases the trust in the product and the people behind it. Gone are the times where you weren't sure when a certain feature or bug fix would be released!

The first sprint in 2016 was a great success! Around 20 team members and Neos enthusiasts met and collaborated on Neos and Flow. Focus points were the React UI rewrite, release management, marketing and project organisation.

This spring is loaded with cool events about Neos and Flow! Make sure you join us at Inspiring Conference and don't miss a sprint, camp or Meet Neos near you.

The biggest Neos and Flow Conference of the year - Inspiring Conference - will happen from 21st - 23rd April 2016 in Kolbermoor. Get your ticket now and don't miss the chance to hear great talks about Neos and Flow and meet the team!

It's that time of the year when wishes come true. Ours are Neos 2.1 and Flow 3.1 bringing collaborative editing, performance improvements, additional languages and PHP7 compatibility.

You might have read that we plan to release Neos 2.1 shortly before Christmas. However next to working on the release there are also plenty of other tasks we take care about. With this article we want to give a short overview on what people are currently working on.

Neos 2.1 is to be released on December 22nd. It will contain a number of new features and a slew of other improvements and bugfixes.

The second Meet Neos 1-day conference took place on 30th Nov in Zurich organized by dotpulse. It was a great opportunity for the Swiss Neos community to get first hand insights into the Neos project, have detailed discussions with team members and share experiences from Neos projects.

New releases of Flow and Neos fix security issues. Users should update to the latest versions.

The plan we made at the last sprint in Frankfurt to adopt an agile project structure reached its next milestone with the forming of three teams. These teams will drive the work of the Neos Project forward in all areas: coding and architecture, marketing and promotion, design and user experience and everything else.

It has been discovered that Neos is vulnerable to XSS attacks and arbitrary file upload.

It has been discovered that Flow allows arbitrary file uploads, posing the risk of attacks. Also a case of potential XML External Entity processing was discovered.

The Neos Project is adopting a Transition Brand Guide to be used while the full brand development process is still ongoing. The Neos Transition Brand Guide specifies a logo text, fonts and colors and thus enables a consistent visual appearance of Neos.

The Neos Community met in the DE-CIX meeting center in Frankfurt for a week-long sprint from 21st to 26th Sep 2015. We decided on a new team structure, worked on the GitHub move, discussed release management and brand strategy and worked on features and bug fixes for Flow and Neos.