Our apologies to those wishing to use the mercurial hook who have been unable to find it. We have restored the hook, and it is now available again by clicking Modules Library in the footer.
Just before we’re about to release our highly anticipated 3.2 version, we found time to do a code-wise small, but impact-wise potentially bigger 3.1.x release. We backported a minor cache fix in our DB layer that may significantly increase the speed for many of you. If you’re experiencing delays (not db index related) or slowdowns, please upgrade to this version (it’s a recommended upgrade anyway) to fix this.
Also in this release is a bugfix for #1419 about non-existing linked articles, a minor bugfix for gmp_val() and a fix for the CLI.
Go get it, here: http://thebuggenie.com/download
In the first and the second blog post in this series, we’ve taken a good look at the generic theme changes and how we’ve worked to improve project management in 3.2. This post will highlight many of the changes we’ve made to the actual issue management. Let’s dive right in!
In the middle of the hectic 3.2 release development, we’ve released a bugfix release for 3.1.x. This release only contains a few (quite visible) bugfixes, and is a recommended upgrade if you’re running 3.1.x.
- Fixes an issue where comments did not appear to be added
- Fixes an issue where removed / non-existant project roles caused project editing to fail
You can download this release from our download page now!
We’re closing in fast on the 3.2 release, and I guess many of you wonder what the changes are. While there have been numerous changes “under the hood”, the most noticeable changes will be the visual ones. And obviously, some parts of The Bug Genie have changed a lot more than others! To help guide you through some of the changes, we’ll have a few blog posts with some side-by-side comparisons with 3.1 vs 3.2, where we’ll describe the changes, and some of the reasoning behind it.
Let’s get started!