Richie, I can sympathize with your frustration. Major releases since 5.0 have required significant effort. We have either asked for a migration effort or introduced new conventions which take time and goodwill to adopt. It's not always a smooth ride as the product evolves.
Your point on improving the release process is well taken. We hope to avoid releasing incomplete or broken version with the following approach: - Rather than planning a release with a fixed feature set and a date, we select a few use cases that we want to support. We communicate these use cases to everyone as the roadmap, giving you an outlook of where the product is going next. https://wiki.magnolia-cms.com/display/DEV/Roadmap - As features on the roadmap get built, we make them continuously available to users on the Magnolia Forge or another non-product channel. We don't put them in the product straight away. This should prevent us from breaking major releases with functionality that has not yet been tested on the field. Such features are not yet be part of the supported product. - After a while, some features will receive positive feedback and we put them in the product. This allows us to pick features that have demonstrable value and have not broken the product. - To make choosing easier, we offer a download service where you can choose the stable product or the latest features. This would allow users to stay on the stable channel if they so wish. In turn, we at Magnolia need to keep our promise and make that channel really stable. Thanks for your feedback, Antti -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=faf63ada-ec7b-4597-a186-0dd92869638e ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
