Version 3.2 beta 3
It’s been a really busy last month. As usual when we release beta versions we get a lot of feedback, so apologies to anyone that hasn’t received an answer yet. The next beta (beta 3) of the upcoming 3.2 version has been a bit delayed since we wanted to finish a significant upgrade in our backend code, namely moving to an updated version of our database layer. Now that this has been completed, and the development version is almost 100% back up and running, we’re working hard to get beta 3 out the door.
We’ve traditionally done one new point-release every 6 months and service releases (.x.x) about every month or so. We’re still on target for a 3.2 release approx. 6 months after the 3.1 release, but the current beta release has set us back about a month from the originally estimated date. With a small team like ours, delays are inevitable, but we really are working hard getting this release finished and ready. 3.2 is such an enormous improvement over 3.1 that we really don’t want to hold it back any more than we absolutely have to!
How can you help?
- Fork us. Fork us on github, send patches back as merge requests or ask to be more involved with the team
- Create translations. Translations are very simple to do, and requires no programmer knowledge.
- Share your own patches and tips
- Donate. Money.
Hopefully a new beta can be released before the end of this week, but please bear in mind that we have day jobs, too 🙂