As of the meeting, we had all the intended features on the roadmap for this release sat ready and waiting to go. There are 7 major features in this release, which is a lot more than we expected to be packing for 0.5.2. All that's left now is to clean up the remaining bugs and blocker issues and we can push this out to the world.
Over the past few weeks, we've made a lot of progress not just on features, but also on cleaning up our backlog of issues on GitHub - even with the ongoing release-bug-finding madness, our issue count sits in the 160s, whereas two months ago that was well over 300. That's not just because we've been closing invalid issues, but because we've struck a great balance between working on issues from the backlog and developing new features. We're building new things and improving the code base and it's all very exciting.
The last week has seen a lot of outstanding UI bugs closed, as well as many more found and raised. We've also crammed in some refactoring and cleanup work to try to make the server side clearer and easier to work with as well as improve the Ghost start up sequence with much better error handling. We hope this will reduce some common difficulties with installing and upgrading by making them much easier to solve.
When do we release?
We're getting asked a lot of questions around when the code base is considered ready for release, when a release is done, and how to know it has been done or find the code in advance.
The first step in being ready for a release is that all the code we want in the release is merged into the codebase. The public roadmap lists the status of all the user-facing features that are intended to be in the release. Any issue or pull request that needs to be fixed or merged before the release is marked with the blocker label on GitHub.
As soon as everything is merged, you'll see a Release Candidate appear on the GitHub releases page. These are orange 'pre-releases', and are essentially the release minus any serious bugs that get found. The RC is created for testing purposes, it gives everyone a stable point to work from to check everything is a-ok.
Once we're happy that the RC is ok, or if there are bugs once they are resolved, the release will then happen at the next opportunity. At the moment, the process is pretty manual, long winded and done by me so it's always started in the morning UK time, this will change in future as we work on automating the release process.
If you're looking to see if the release has happened yet, the first place the release will appear will be on the GitHub releases page, followed by npm, the stable branch and Ghost.org. Meanwhile, Ghost(Pro) blogs are upgraded in the background.
With 0.5.2 nearly ready for release, it's time to start looking at what will make it into the next feature release. The roadmap is fully loaded, continuing the split focus between improving the admin panel to provide more features like auto save and the filter menu and adding enhancements to the theme API such as adding open graph tags and other structured data by default.
If there's a feature you'd like to help us build, come visit us in IRC and we'll give you a hand getting started!
What is this?
We hold a public development meeting pretty much every Tuesday at 5:30pm London time in the #ghost channel on freenode. In this meeting we discuss progress, important issues, and what is and isn't on the Roadmap. It's a chance for everyone to get involved and have their say about where Ghost goes next.
Hope to see you at next week's meeting: Tuesday 30th September, 5:30pm London time.
Subscribe to Ghost Dev
Get the latest posts delivered right to your inbox