"Buying" a ticket wouldn't have raised the priority in this case, since the ticket in question is a Medium. Tickets get reviewed by order of severity in a pair of weekly meetings. We review all the new Blockers for Core and Enterprise, then the Criticals, then the Mediums and so on. We average about 40 tickets a meeting and haven't made a lot of progress on the Mediums and the Lows haven't been touched. Once a ticket has been reviewed it gets either closed (duplicates, already fixed, not reproducible, etc.) or it goes into the backlog for the relevant release (current maintenance 2.3.X or next release). Developers juggle their time between working on features for the next release, bugs against the maintenance release and the next major release. If you look at the release notes most all the tickets that get closed are Blockers and Highs and we don't ship with any of those open against the release. 2.3.3 is close to being released, 2.4 is scheduled for 2nd quarter of the year.
We're altering the format of the review to raise the priority of tickets with patches attached. I wrote myself a note on Friday to bring up your tickets in the next review. Thanks, Matt Ray Zenoss Community Manager community.zenoss.com [email protected] _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
