Dev call May 11th, 2011

, Will Kahn-Greene | share this (mastodon)
Note: This is an old post in a blog with a lot of posts. The world has changed, technologies have changed, and I've changed. It's likely this is out of date and not representative. Let me know if you think this is something that needs updating.

Miro 4.0 status

  • roadmap

  • we're working on a rc for today

  • we're tentatively planning a rc for next week

  • we're hoping to release on May 23rd

Will:

  • worked on P1 bugs, synced translations, did peer reviews

  • coordinated release candidate work

  • had the flu

  • fixed the keys on his Macbook except the spacebar

Jonas:

  • worked on app indicator support and other P1 bugs

Goeffrey:

  • worked on performance issues and crashes related to sharing

  • planning to look at OSX Lion support

Paul:

  • worked on device issues/crashes and ui issues

  • waiting on information that we'll get in the next release candidate

Ben:

  • fixed a bunch of issues

Kaz:

  • worked on a ton of P1 blockers

Janet:

  • did a ton of testing

  • worked on automated testing which is working pretty well

Order of business:

  • rc1 today

  • rc2 may 18th?

  • Miro is developed by a community of people including you! If you can't contribute your time and work to development, testing, and translations, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects like Miro Community and Universal Subtitles. See http://pculture.org/about/ for more details on these projects.

  • Did you know there's a Miro User Manual? If you haven't looked at it yet, it's worth taking a look at. You can find it at http://manual.getmiro.com/ .

Bugzilla stats for Miro for the last week:

  • 99 bugs/feature-requests created

  • 4 bugs marked WORKSFORME

  • 9 bugs marked INVALID

  • 6 bugs marked DUPLICATE

  • 1 bugs marked WONTFIX

  • 81 bugs marked FIXED

Unrelated side note

I finally added the rst plugin for PyBlosxom to my blog so now I can post in restructured text rather than HTML. Yay!

Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.