Hey,
is there something in the release pipeline for data-versioning/version-controlling in Neos?
In roadmap I only can see the version life cycle of Neos not the planed features.
Is something like «new features for version XY» somewhere to look on?
Is node-data-versioning planed or implemented in v3.0 or usable with some Package?
(In “nodedata” table I can see the “version” column. Maybe there is a solution to use)
In addition to new features and hundreds of improvements, Neos 3.0 and Flow 4.0 will come with …
A list or something similar would gave me an idea about the effort of the 3.0 upgrade (without install and try and error stuff). Also for an own-code-change “cost use bill” for do current project upgrades. Would be great someone could gave me a hint in the right direction.
As an open source project we can neither predict nor dictate what contributors work on, therefore we cannot give you a date and promise features currently. We decided for dates for now and do not define which features will be in the release. We have a few core areas we are working on though and nodes with history (key point event sourcing) is in the works but is a big effort.
You are right though that we could give a list for the upcoming release Neos 3.0 and Flow 4.0. I don’t have one from the top of my head but I guess we can collect things…
Of course.
Thought there might be something like a community-internal sort of wish-plan or estimated/desired level-target points, which is written in some slack- or forum-post: Which I can’t find, because I’m looking for the wrong terms.