In June, I told about the consolidation of the MariaDB project tools. The final piece of this consolidation, to report bugs in the MariaDB project tracking tool called JIRA has now been finalized.

Bug reporting stays open! JIRA is open to anyone. The bug reports are publicly available, even without logging in and as a bonus it will be easier to follow what is going on in the project since you don’t have to jump between several tools to get the complete picture.

All bugs that existed in Launchpad have been migrated to JIRA. To find a bug that was originally reported on Launchpad use the following approaches:

  • If you happen to have the original bug id you can search for the bug by typing lp:bugid into the search field in the upper right corner of JIRA. Also, if you have the link to the bug report on Launchpad, you’ll be able to open that bug report and get hold of the id (which by the way also can be seen in the URL).
  • You can also search on keywords, e.g. “ALTER TABLE” or “microsecond”
  • In addition JIRA includes a nice search functionality with which more advanced searches can be done like searching for issues reported by a specific user. This search is found in the top navigation under “Issues” and is called “Search for issues”.

Getting the bugs into the project tracking tool of MariaDB can be seen as an enabler of the personal task I set for myself in my MariaDB Directions blog post last week, on creating a longer-term roadmap for MariaDB. Now with the development tasks, bug reports and planning inside the same tool, anyone can see what is going into which version of MariaDB.

Please make yourself familiar with MariaDB development by checking out JIRA and do participate in the development by:

  • Creating new issues in JIRA for features you would like to see in upcoming versions of MariaDB
  • Reporting possible bugs in MariaDB, “Create Issue” in JIRA
  • Commenting and adding more information to existing issues in JIRA

You’ll have to create an account for yourself to do that, which is very straight forward. Just click on the Sign Up –link in conjunction with the Login and follow the instructions.

If you did report MariaDB bugs on Launchpad before you’re also seen as the reporter of the bug in JIRA and an account has automatically been created for you in JIRA. However this account doesn’t hold your email address, since it was not (easily at least) possible to export that from Launchpad (probably because of privacy reasons). We are glad to activate your automatically created account in JIRA. Todo so please send us your name and email address through the Monty Program contact form.

 

It is not a secret that we’ve been kicking the tires and playing with JIRA for project management. After using it since the beginning of the year most of us like the feel of it and we’ve decided that it makes sense to start using it more.

As you know, the MariaDB project has many fragmented resources. We report bugs in Launchpad. We store our plans in worklog. We’ve never used the Launchpad Blueprint feature for this very reason. We don’t use Launchpad Answers because we have the Knowledgebase.

With this move to hosted JIRA (yes, this is an important link: http://mariadb.org/jira) we can report bugs, have future plans, and also give users a roadmap which is pretty cool. One nifty feature is that in the past two releases, we had a roadmap and we didn’t slip in terms of a schedule. We had on time releases and that’s awesome!

So what does this mean for you? To report bugs, you will now do so on JIRA. To make feature requests and talk about our future plans, you will also now use JIRA.

We plan to deprecate Worklog and Launchpad bugs by 30 June 2012. Launchpad will however continue to host the source code for MariaDB.

What will happen to bugs already reported on Launchpad? We have migration scripts ready for this and when we press the button bug reports will nicely migrate over to JIRA. After that is done we’ll place a notification on the MariaDB bugs page in Launchpad about reporting new bugs in JIRA.

What will happen to feature requests and ideas already in worklog? Worklog will be put into a read-only mode and there will be notifications about the move to JIRA. Whenever needed we’ll copy & paste worklog items into JIRA.

What does it mean to the openness of the MariaDB project? It’s not affected at all. The MariaDB project will remain an open community friendly project and as a bonus it will be easier to follow what is going on in the project since you don’t have to jump between several tools to get the complete picture.

The consolidation to JIRA provides the means to report and track project status easier than before, which allows the MariaDB team, community members and other to better coordinate and prioritize work.

As a side note, JIRA (and other software by Atlassian) has sometimes been criticized in the open source world because of its commercial nature and many are unaware of the fact that Atlassian do offer a free Open Source Project License to open source projects, which is what is being used with MariaDB.

As another side note, I’m not going to dive into comparing features in e.g. Launchpad with features in JIRA. I do know it would be possible to use blueprints for feature specifications etc. in Launchpad. The most important aspect in my mind is that you pick a tool that you like the feel of, has the features you need and tightens collaboration between developers, project managers, community members and other persons involved in the project.

In short, this is all about three project tools becoming one.