It’s now 4 months after Codegarden and we’re very happy to that version 4.11.0 is eagerly knocking at the door. 4.11.0 delivers what we promised you at Codegarden: a strong comeback of Umbraco 4 with full MVC support. We’re very proud of that. Even better: the reception of 4.10.0 both in- and outside of the community has been very positive.
Another thing that we’re very happy with is the great number of contributions we’ve received from the community. It’s very satisfying to be accepting bug fixes for things that people have been annoyed by for ages and finally now they feel empowered to try and fix them. We’ve been trying to help everybody who wants to get involved out and the effect has been an explosion of pull requests and patches. Thank you, thank you, thank you. Awesome work!
With our new (more agile) focus we’re also regularly doing reflection on what works and what doesn’t work. This has led to a few discussions within the core team to see how we can improve our process and we came to a simple conclusion: we’ve been wanting to do too much in too little time, we need to pace ourselves.
We've also had feedback from the community saying that we’re releasing a bit too often now and people can’t keep up. Very fair feedback and we’ll be releasing less aggressively.
- We love that we’ve been able to put out the recent releases with good quality but want to do better
- We’ll soon relax the release schedule so you can keep up again
- No more breaking changes between major versions allow you to upgrade with confidence
This means that we’re going to change the roadmap a little to adjust for these new insights. In practise, this will lead to a more agile way of doing things, we’ll be putting less work items in each sprint.
We still have an overarching vision of where we want to go, but very specific smaller tasks won’t be set in stone. So the big things that are upcoming are (in order of appearance):
- New low-level and high-level APIs plus improvements to the MVC bits
- Project Belle, the new user interface
- Concorde, Umbraco as a Service
With regards to the release schedule, we’re relaxing that a little bit after v6.1.0. We’re really eager to get the new API’s in the hands of everybody and deliver all that we promised for v6: new routing, new api’s, new business layer and MVC, which is exactly what we wanted for v5.
As of 6.1.0, we’ll still be doing sprints of 2 weeks with the team, leading to a deliverable after each sprint. We’ll be doing actual releases every 8 weeks though, this will be either a major or a minor release.
Speaking of backwards compatibility, we had so many things that really, really needed to be fixed in v4, that we bended the rules of SemVer a little and introduced some breaking changes in minor releases. We realize that it’s not been very consistent with our own guidelines, and as of v6 we’ll only make breaking changes in major releases, so you will be able to upgrade with ease.
A lot of people (especially Jeroen) actually like our fast release schedule and don’t want to wait weeks to be able to take advantage of the improvements we’re making. Because we’ll have no breaking changes, it will be safe to upgrade to nightly releases, so that’s what we’ll be recommending from now on.
As for breaking changes, we’re allowed to break things for v6.0.0. And we will, but we’re trying to keep them minimal. The main changes will be around the database and these will be handled by the installer during the upgrade so it shouldn’t be too painful.
We realize that while our main job is to produce software, you job is to both understand and implement our software. We'll be easier to keep up with, giving you more time to learn, understand and build.
And with that: go forth and make awesome websites!