We have a bug-review every week (usually on Thursdays), the ticket will get triaged there. It sounds like a high priority regression, meaning it would probably get marked for patching into the next 2.3.X maintenance release rather than Blue Crab. A developer will probably tackle it within the next week or so. Once the fix is in, you could use zenpatch to get it before the next maintenance release. Assign it to me when you open it.
Thanks, Matt Ray Zenoss Community Manager community.zenoss.com [email protected] On Jan 13, 2009, at 3:23 PM, crosse wrote: > > mray wrote: >> Go ahead and open a ticket on http://dev.zenoss.org/trac/ There >> are a >> pair of SNMP trap tickets already verified for 2.3.3: >> http://dev.zenoss.org/trac/ticket/4183 >> http://dev.zenoss.org/trac/ticket/4219 > > I have a feeling I know the answer, but I have to ask it anyway: > once the ticket is opened, do you have an idea of how long it will > be until a fix will be made available? At this point I'm staring at > a console where fully 40% of all current events are broken SNMP trap > events. :-( Is it worth the trouble of downgrading back to 2.2.4 at > this point? > > Thanks for all your help thus far, > > --seth _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
