jmp242 wrote: > I'm used to commercial prioritization of bugs, and to be honest, this seems > like a medium level bug to me, especially with now two work arounds. So, > really - this isn't that egregious an issue IMHO.
I would agree, if it were the only issue with maintenance windows and schedules. That code just seems buggy as all, and I've seen the same issues go unfixed since the 2.0.x days, even while new eye-candy made its way into the product. That's really where my current beef lies. jmp242 wrote: > Secondly, at least for the Core users it's 0 money, and it's OSS, so if you > were totally bugged by it, the normal saw applies. You could fix it, you > could pay someone else to fix it *and* you can submit it upstream so it is > fixed. No one apparently cared enough to do that, so we waited a little. I think I was told in one of my posts about maintenance windows not working properly that I could do just that--either fix the code or get a support contract. We went with a support contract, and currently have a case with the title of 'Zenoss does not always honor "Original" Production State for Maintenance Windows', and everything that that entails. We currently have a developer assigned to the case, who stated in his last update that "there's a sketch of an algorithm for addressing maintenance windows in a more generic way under discussion." So, hopefully a lot of the flakiness with maintenance windows will be fixed soon. And the great news, especially for Core users? Since the bug(s) in question exist in Core, they'll get fixed in Core, and everyone else will get to benefit as well. I look forward to working with the developer on getting this resolved. I'm actually pretty excited, honestly. Another ticket we submitted to Zenoss was about the WMI issues with 2.2.1 (remember all the "threshold of zenwin cycle time exceeded" events?), which resulted in an identified bug ( http://dev.zenoss.org/trac/ticket/3428 ) and the resulting fix. I relate all of this so that hopefully you can see that I do what I can: I try to submit tickets against those things which I find to be buggy, and which others have found to be problematic. jmp242 wrote: > I just keep hoping we'll see more community development occur, and I think we > have as time has gone on. I hope so, too. I honestly wish I could help, but my coding skills are...well, let's just say they're sub-par and leave it at that. This is one of the reasons that I recommended that JMU buy Enterprise (and then submit tickets against the bugs that we find in core areas of the product). I wanted to be able to contribute to the project, and that was the best way for me (us) to contribute. --seth -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=32054#32054 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
