[Dev] Chandler 0.6.1, bug council, and targetting bugs in bugzilla

[Katie Capps Parlante]

As Heikki mentioned, we're planning a 0.6.1 release for Feb. 9th. This 
release has two goals:

(1) Fix bugs that prevent target users from dogfooding chandler. In 
particular, Mitch and Esther are trying to use Chandler day to day, and 
a few bugs are getting in their way. Also, some CSG members were unable 
to get data from Oracle calendar into Chandler, and we'd like to fix 
this so that they can start dogfooding and giving us feedback. We won't 
tackle bugs that are expensive or risky, or fix all bugs relevant to the 
0.6 tenets -- just the ones that prevent real users from giving us feedback.

(2) Fix problems (bugs or documentation) that get in the way of our 
PyCon sprints. For example, we're planning on fixing documentation and 
small code bugs that people noted while trying out the tutorials. We're 
planning on using 0.6.1 for PyCon sprinting, so this is the last shot to 
fix any problems.

Anyone can nominate a bug for 0.6.1, based on the above criteria. To 
nominate a bug, set the "blocking0.6.1" flag to "?". If the bug council 
accepts the bug for 0.6.1, we will change the flag to "+" and set the 
Target Milestone to "0.6.1".

As always, you can look at the top of DevelopmentHome for convenient 
bugzilla links (used by bug council):
http://wiki.osafoundation.org/bin/view/Projects/DevelopmentHome

The Chandler bug council meets on Thursdays at 4pm (PST). The current 
regular participants are Sheila, Heikki, Aparna, Philippe, and myself. 
Anyone can ping us in irc at that time. We will review all bugs 
nominated for 0.6.1 and all untargetted bugs, and take a first pass at 
targeting bugs to "0.6.1", "0.7" or to "Future", based on the current 
tenets. Please add comments to bugs when you have relevant info, so that 
bug council has the information to make good decisions. Similarly, the 
bug council will try to document all decisions and reasoning in the bug.

Cheers,
Katie