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. I mean, this happens 2 times a year, so there's been what, 4 occurrences since this was reported? I've had bugs in similar costing (and of course, for me in Core way more expensive) products like AutoDesk Inventor and their data management server that had me manually doing something every day for over a year. I've had major bugs that make it unusable for 64 bit when it's advertised as 64 bit ready for months and months.
So, really - this isn't that egregious an issue IMHO. 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. With closed source companies like Autodesk above, we couldn't have paid more to get it fixed quicker if we wanted to. Now, if you're a paying customer I can see being annoyed like I was with Autodesk in my example, but I still can't see something this rare (twice a year) being that big a deal. I just keep hoping we'll see more community development occur, and I think we have as time has gone on. -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University crosse wrote, On 3/5/2009 11:40 PM: > mwcotton wrote: >> I think the fact that this problem has not been fixed, after many months, >> and we see other silly features pop in the releases says alot. > > > Honestly, I'm glad someone else sees it that way, too. I didn't want to say > it myself because I've done quite a bit of drum-beating about this in the > past (not just related to DST). I'm sure the eye-candy gets requested by > paying customers, but to put some of that stuff in while there are still > glaring bugs that have gone for more than a year without being fixed still > bothers me. > > That being said, I have a case open with Zenoss about one of my biggest > problems regarding maintenance windows, and I have high hopes of it finally > getting fixed (15 months after I first reported issues with it). > > Of course, I still think Zenoss is one of the best products out there for > enterprise monitoring--if not they best, period. I just wish sometimes that > the eye-candy would get put on hold until the show-stoppers get squared away. > > --seth > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=31970#31970 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
