6.0.6 Release Date Pushed Back?

[LMStone]

I see that the product portal now shows 6.0.6 being released on 10 April 2010, whereas earlier this week 6.0.6 was scheduled to be released on 29 March 2010.

I know the dates in the product portal do not represent firm commitments by Zimbra, and frequently do shift as this one has done.

But we do have a few pending installs we were planning to do next week, so this two week delay does change things for us.

Can Zimbra provide any kind of guidance as to whether the 10 April date is likely to change again, as well as what it is that is causing the 29 March date not to be met?

Thanks!
Mark

[bdial]

yeah i've been watching it like a hawk a bit. yesterday it went from 2 open issues to 7 so the push back didn't surprise me. like this was just reopened today

Bug 43918 – Need right to allow 'View Mail' for resources

so i imagine even if they get everything fixed theres just not enough time with the weekend coming up to QA it before monday.

[mmorse]

Decided it would be good to get in the just discovered http://www.openssl.org/news/secadv_20100324.txt as well. Wrapping up some final 6.0.6 open items, 5.0.23 had been sitting ready for a while but there's always a 'one more'. All three releases are currently scheduled for the 5th (rather than 10th).

EDIT: Er the 8th, fluctuating medium ground.

[aner]

Any updates on when 5.0.23 and 6.0.6 are coming out? We had planned to
deploy 5.0.23 today but the 5th came and went and I have seen no news
on the new releases!

[phoenix]

Originally Posted by aner

Any updates on when 5.0.23 and 6.0.6 are coming out? We had planned to
deploy 5.0.23 today but the 5th came and went and I have seen no news
on the new releases!

ZCS 6.x
ZCS 5.x

[uxbod]

Perhaps, Phoenix, I should ask which TZ as it is the 8th

[phoenix]

Originally Posted by uxbod

Perhaps, Phoenix, I should ask which TZ as it is the 8th

Local Time Zone for Zimbra HQ.

[dave_kempe]

Which is San Francisco or thereabouts.

[sugiggs]

What does it mean verified in product portal?
Verified already fixed or verified it is a bug/issue?

because one of our bug is placed under Fixed issue but the status is verified.

[bdial]

verified means that the fix has been verified to work on the release