Last week, we released version 3.2.7 (and 220.127.116.11 to hotfix an upgrade and installation issue). This release is a collection of all the development that has happened in the 3.2 version since last release which was almost a year ago.
There’s no need for releases to be this far apart, and we’ll try to not let it happen in the future. In the meantime, in this release you can enjoy:
- Improved speed and stability
- A whole slew of translation improvements
- Support for PHP 5.5
- Support for logging in via Mozilla Persona
- General bugfixes
Until next time!
This blog post will start out with an apology. The Bug Genie version 3.3 has taken considerably longer to finish than I first imagined. Most of you who follow The Bug Genie are familiar with software development. As is often be the case when you are working on a growing project, areas of the code and the application needs to be improved and added to, in order to both maintain scalability, usability and to add and improve features.
The Bug Genie has been at a stage where a lot of the backend code needed to be refactored and to be improved. There are several things and features with The Bug Genie that are really awesome, but there are also quite a few areas where we simply aren’t doing our best. Notifications, authentication, permissions, file uploads, mobile – these are just to mention a few. In the age of html 5, usability first and “competing” software improving at a rapid pace, The Bug Genie needs to both lead and follow. Lead, by showing that open source issue tracking and project management can look – and be – as good as proprietary alternative. Follow, by not lagging behind in features or usability.
Version 3.3 started out as a medium-sized improvement over 3.2, about the same as 3.2 was over 3.1. There was a time during 3.2 development where using 3.1 was becoming a pain. The improvement in features and functionality in 3.2 was just too much to keep using 3.1, once you’d made the switch. This is where 3.3 has been for several months. Version 3.3 – as an improvement over 3.2 – is more than finished, but it’s not there yet. There are still things that needs to be addressed, improved and changed. I’d like to keep improving and fixing, but at some point you gotta say “dude, release it already”.
3.3 just won’t be all it has been promised to be during the last year of development. Too much time has gone since we started, and too many things have happened to keep our initial targets. But it will be a great improvement over 3.2 – so much, in fact, that I can almost guarantee that you will have no reason or desire to switch back.
Now, for the update. During the last couple of months, the search frontend and backend have seen a complete rewrite with focus on finding issues immediately, instead of old-style “searching”. You’ll see what I mean once you get your hands on the beta. Also, mail notifications have been improved, with the introduction of “notifications”, and a much simpler notification setup for email notifications. In addition to that, a great number of improvements are happening in the backend to improve performance and security for all our users and usecases. In addition to this, the default theme has seen several tweaks and changes to improve readability and usability.
I’ve attached a couple of screenshots of how it currently looks. Keep in mind that some of this may still change, but I think it’s starting to look solid. I hope you like what you see – and if you want to help out with development or testing, feel free to check out the master branch on github.com/thebuggenie – pull requests are highly appreciated.
Until next time!
The 3.3 release is getting closer, as you can probably tell from the activity in the bug tracker and in the git repository. While the 3.3 development version is not ready for public testing yet, it’s time to tell you about another new, cool feature coming in 3.3:
Markdown syntax support!
Just a heads up to anyone thinking about trying to start a blog post series just before summer: not a good idea. Anyways, I’m back with another update on new and upcoming features in 3.3. Many of you may not use the wiki, either because of its limited abilities to format and organize content in it, or just because you use another system for documentation or don’t have wiki content to put in. Fair enough, but in 3.3 a huge push has been made to make it possible and desirable for you to put your documentation and text content in the Bug Genie wiki! How so?, I hear you whisper in the shadows – oh, I’ll tell you.
The 3.2 wiki – while staying compatible with the Mediawiki (Wikipedia) syntax – only contains a minor subset of the full syntax available in Mediawiki installations. The goal with using the Mediawiki syntax is both to make it easy to use the Bug Genie wiki for Mediawiki users and authors, and to not introduce yet another wiki formatting syntax for you to learn. The mediawiki syntax is straight-forward, feature-rich and easy to understand. About time we started supporting more of it!
So, what have the wiki got in store for you for 3.3? Read on!
First of all, I just have to say sorry for not keeping this blog more up-to-date. There has been much to do with both life and work, and little time to blog. That’s about to change, so this blog post should hopefully work to liven up the blog again.
Now, with that out of the way, you’re probably wondering what is happening with the next planned version – version 3.3 – originally scheduled for release early this year. As you may have noticed, instead of launching version 3.3, I started a donation campaign to try and attract some attention to the fact that The Bug Genie is unfortunately a one-man show nowadays with little help from the outside. I will tell you how that went in a different blog post, but rest assured that version 3.3 is coming, and it’s closer now than it was in January!
When you upgrade from 3.2 to 3.3, you will probably not notice anything new directly on the frontpage – but as soon as you start navigating around, you’ll see what’s been keeping us busy.
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.