Three years ago we started posting regular weekly updates
about our progress with Doomsday. The goal was to keep ourselves and everyone else up-to-date while we worked toward stabilizing the code base after a long beta period.
However, circumstances have changed since then. We have our own issue tracker
for project coordination and planning, a relatively high-quality master branch, and we do our work mostly in private work branches. The need for weekly updating has decreased, and for a long time now, I've been the only developer doing it regularly. Thus I did some rethinking on the subject
, and concluded that a different kind of blogging convention would be more suitable.
I will stop posting weekly updates. Instead, whenever something of significance is merged to the master, we'll write a post about it. Since our objective is to merge ongoing work to the master every couple of weeks, this should still result in regular blog posts, although not as regular or frequent as before.
Another important component of my weekly posts has been details of what I've personally been working on during the preceding week. I like sharing this stuff with you, however doing it on a rigid schedule is not ideal: I've had to write it in a hurry and mostly based on the memory of the past week's events; sometimes having to browse though the week's commits to see what actually was done. Some of the most important insights or notes have been forgotten by the time the post was written.
The best solution I came up with was to move my personal progress to my own blog, where I can be as verbose as needed, and post conveniently whenever I have a suitable opportunity or need to do so. This should result in a more detailed, albeit also more difficult to follow journal of my work on the project. If you are interested: