Thanks Greg, and yes, we are planning on releasing Minor (feature) versions with a 3 month minimum interval to more effectively release new features and have more time to user test them and iron out any early bugs as much as possible. We also have some more information on how the version releases are changing for Matrix 5 in this weeks newsletter (publishing tomorrow due to Good Friday public holiday) and what each version number means.
So you release something and if it contains bugs than Squiz won't let the user install the latest version if they are not on the Connect / Partner scheme?
Anyone can install any version of Matrix. We're not going to prevent anyone from doing what they already can with the code, none of that is changing.
We've had the public CVS repository open for a long time now, over 10 years I believe. And in all that time, we've had very little code contributions coming in from the developer community. This is mainly because the Matrix code community is very small. Continuing to keep the versioning system public is actually an overhead for us as there is a management aspect that comes with it. If there is no return on this investment, then it doesn't make sense for us to keep going down that path. We much rather invest in the systems and the people that want to actively contribute to the software and reward them for it as well.
There is also a security aspect and risk that comes with our current model that we are addressing with this change. By not publicly exposing every single bug fix and security patch that we apply, we are making it harder for attackers to know about these potential exploits to vulnerable sites. At the moment, we don't have the resources or benefits to continue to manage this on a public level.
If you still have questions or concerns regarding this change, I'm happy for you to contact me directly via firstname.lastname@example.org to discuss further.
We are trying to as open and honest about this as possible.