First Mumble Tracker Squash Meeting

Over the past few months, most of the Mumble team has been busy with other projects. This has lead to an unfortunate build-up of unsolved bug and feature requests. This Sunday, we had our first developer meeting to address this.

Every now and then, real life and other projects have to take priority over Mumble development. Since about mid-march, the only requests we’ve really done anything about has been patches. Bug reports and feature requests have been put on the “todo” list, which by now has become pretty long.

In an effort to address this, this Sunday saw our first developer meeting (held using Mumble, of course). This saw quite a few results, which I’ll go through in turn.

First of all, 1.2.3 is now more or less feature komplete. Krejler has a block of OSX interactive overlay code that is missing, and .D0T, pcgod and other contributors are working hard on finishing an initial version of audio recording. The current plan is to get these features in, resolve any bugs that remain and then release 1.2.3. With a bit of luck that will happen inside of a month.

As a consequence of the above, that means the 200 feature requests we currently have unresolved in the tracker will not be addressed for 1.2.3. Once 1.2.3 is out, we’ll start going through the requests and implement things that look fun or make a lot of sense. In the meantime, we’re currently evaluating replacements for the feature request tracker itself. While the tracker works well for bugs, it lacks a few features we’d like to see for feature requests, such as popularity tracking, milestone targets and easy marking of duplicates. SF.net is currently implementing SF.net 2.0 and maybe that will improve things. If not, we’ll probably need an alternative.

Most of the meeting was spent triaging bug reports. All bug reports should now either have been assigned to a developer for fixing, set pending with request for more information, or left open because triaging them takes a lot longer. As it turns out, this triaging is a good thing, as it allows all of us to work independently on fixing specific bugs, which means we should have a fairly bug-free snapshot ready inside of a week.

This entry was posted in Uncategorized. Bookmark the permalink.

9 Responses to First Mumble Tracker Squash Meeting

  1. Pingback: Mumble: Die Entwickler melden sich zu Wort… 1.2.3 :D - NatenomĀ“s Blog

  2. SuperRoach says:

    Wow, implementing recording before the release of 1.2.3 sounds fantastc, almost as much as having 1.2.3 out so the rest of the people can try out it’s amazing overlay feature.

  3. Megagoth1702 says:

    Recording? lol, now I can show people what true noiseless quality sounds like!

  4. Pingback: muppfarmen.se » Blog Archive » Mumble 1.2.3 is coming

  5. Pete says:

    Try out JetBrains’ YouTrack for your tracker; there’s an open-source licensing option. And it’s really rather good.

  6. Lake says:

    I would much rather have 1.2.3 out the door with its new overlay (and priority speaker) than wait on a new feature implementation.

    I want to start introducing new folks with 1.2.3 directly, and this would save me the trouble of finding a particularly stable build to direct them to.

    • .D0T says:

      @Lake: We want to get 1.2.3 out the door just as much as anyone else but I think it is worth waiting for the integration of much requested features like recording (which you’ll see it in snapshots very soon). Also, if we want to release for all platforms at the same time (which we do), the OSX overlay has to catch up first (krejler is making good progress on that).

      It is an unfortunate fact that this release, for reasons explained by this blog post, took a lot longer than our previous releases. We don’t like it either and hope this will stay an exception so stick with us this time.

  7. Pingback: For the record | Mumble

  8. wonderer says:

    When will it be ready? Its another month, so … :-) I do not want to stress you guys, but I think we all want that coming out hihihi.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>