Dev (#6) - 0.6.00 Release (#37) - Message List

0.6.00 Release
 unsolved

I've been hitting CWiid pretty hard for the past couple of months with the API rewrite, python extension, and python plugins, and I've got the functionality where I want it for a 0.6.00 release. Here's the gameplan:

  1. Leave the code in /branches/dev for a week or so to let devs find the easy bugs.
  2. Merge into trunk, leave for as long as bugs keep rolling in, and for me and whoever else wants to help to clean up the code (debug Python reference counting, clean up error messages, comment, etc).
  3. Release.
  4. Obligatory reference to ridiculously tired and no longer funny South Park joke.
  5. Profit.

Note that this is more of a personal feature freeze than a global one - if anyone else wants to work on stuff, I don't have a problem incorporating it as long as it's well tested, but I've got other responsibilities that need to take priority for a little while. Two issues in particular I'd like to see resolved:

  • Accelerometer LSBs
  • Automatic Wiimote discovery problem

It's been my hope that once we had Python to make plugin development easier, more people would contribute to development, especially tracking, which has been too bad for too long. At the least we could copy the algorithm from WMD (with due credit, of course).

Questions? Comments?

  • Message #170

    /branches/dev has been merged into /trunk

  • Message #173

    I think we've got almost everything I really want for a 0.6.00 release, with the exception of a decent IR tracker and the accelerometer LSbs. I can live without the latter, and I'll take a stab over the next week or so at the former (I think a single source IR tracker may be a good interim solution). So, the main question is, in my mind, how do you go about releasing such a radical change? Should we put out a 0.6.00-rc1 first, or just put out 0.6.00 and see what happens? I'm not getting much feedback from developers regarding stability and bugs - is this because no one is testing the code, or because it's that good ;)? If you've tested the trunk code and can offer an opinion on whether or not it's ready for release, please post here.

Attachments

No attachments created.