Dev call 1/27/2010 minutes

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.0 status (roadmap) (was Miro 2.6)

  • we're really close to a release candidate now--just squaring away some issues that have popped up and letting the code bake

Miro Community 1.0 status (roadmap)

  • we're working on 1.0 now--probably a 4-6 week dev cycle


  • Fixed bugs.

  • Feeling great about 3.0.

  • Has a few more things to do, but is pretty much set for 3.0 things.


  • Fixed bugs for 3.0.

  • Worked on testing. Started seeing memory leak issues.

  • We can release even with the Perian issue as long as we mention the issue in the release notes.


  • Going through testing and bugs and keeping up with changes.

  • We're really close to release-candidate worthy.

  • Worked on performance testing and testing on OSX--lots of performance fixes in 3.0.


  • Fixed bugs.


  • Worked on Miro Community post 0.9 issues.

  • Now working on 1.0. Looking at a 4-6 week time frame.


  • 33 bugs/feature-requests created

  • 3 bugs marked DUPLICATE

  • 23 bugs marked FIXED

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.