Dev call 9/8/2010 minutes

, 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 3.5 status (roadmap)

  • focusing on P1 issues and trying to get the release done

Miro Community 1.1.2 status (roadmap)

  • focusing on small bugs that should get fixed before the long haul for 1.2.

Paul:

  • reviewed Miro Guide patches

  • worked on Miro Community fixes

  • talked with Anne and Dean about Miro Community future

Janet:

  • worked on Miro 3.5 regression testing focusing on OSX

Luc:

  • worked on OSX issues

  • looking at P3-P5 issues and worked on them

Ben:

  • lost his Internet connection

  • worked on bugs anyhow (git ftw)

Will:

  • peer reviewed and fiddled with conversions code

  • worked on the libfaac bug

  • fixed the Windows system tray suckage bug

Order of business

  • We talked about the Miro 3.5 schedule. We're focusing on P1 bugs only at this point. Nothing should get added to the list without discussion.

  • Priority is being put on finishing development work on Miro 3.5. Any help with this would be huge. There are a series of bugs on the roadmap that need to be fixed. If you want to help out but don't know where to start, see http://getmiro.com/userguide/contributing.html. If there are bugs you want fixed that aren't in our queue, consider submitting a patch.

  • If you can't contribute work, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related 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://getmiro.com/userguide/.

Bugzilla stats for Miro:

  • 11 bugs/feature-requests created

  • 7 bugs marked FIXED

  • 1 bugs marked DUPLICATE

  • 1 bugs marked WORKSFORME

  • 1 bugs marked INVALID

  • 12 bugs marked INCOMPLETE

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.