So the ticket for fixing this was opened very late in the 2.3 beta  
process, right around the end of DST last year.  We decided not to  
delay the release and include the fix in 2.3, and the patch was  
rejected for 2.3.1 because we thought we'd have 2.4 out before DST  
rolled around again.  Turns out we were overly optimistic on the 2.4  
release schedule, so here we are today, using a work-around.  I'll go  
ahead and say that 2.4 will be out before the next DST switch :)

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

Reply via email to