Hi all,triggered by the discussions we had about new features, important changes and when/where to implement them and also Jacopo's question about the framework/plugins release strategy, here are some thoughts about our release strategy in general:
In the past we created a release branch every year (with the exception of 2019), just starting where the trunk was at the time.
Maybe we should start building a roadmap naming features we want to have in the next release and create the next release branch when we see it is the right time (looking at the *features*, not the time period). This would make more transparent and calculable to the users which changes are to expect in the next release and how the project evolves.
A good roadmap would include a mix of core development tasks (making the framework better, new features in the applications and bugfixes). I can image a roadmap with certain goals might also motivate more contributors to work together on announced features and finish a release. It could also help to better organize community days and help organizing the development of long term changes (e.g. changes for a new deployment strategy, huge refactorings etc.).
We should also better track the deprecation of features/API etc. so that we are able to better communicate when deprections will be introduced and executed.
This all means a bit more planning and discussion in the community but could help to better join forces, work together on certain goals and provide a clearer vision about the project's roadmap in general.
What do you think? Regards, Michael Brohl ecomify GmbH - www.ecomify.de
smime.p7s
Description: S/MIME Cryptographic Signature
