To truly consider it 'locked/final' you'd have to wait until NE is out - as you know we like to release FOSS a little earlier for feedback & more quality assurance time. For instance, there might be a few things we want to consider squeezing in. Often they're things QA doesn't consider to be blockers for a FOSS release, but we know NE customers would appreciate us getting in before a long wait to a next release. (And such is the nature of deal breakers.) Sometimes they may be network only components that need fixes, but there might be some related open source code changes too.
As we don't pre-announce dates I realize that makes it difficult to time a 'same day' Community release, but there's nothing to loose by grabbing code for your final build the day after FOSS is live, as opposed to creating builds beforehand and people asking "did this make it in?"
That said, using
Zimbra Time about now you could start kicking off a Community build release candidate - as FOSS timeline is:
Quote:
Today - Tonight at 11:59PM (we didn't give a timezone)
Coming tomorrow morning - Still morning in India right?
Tomorrow - By 5:00PM that day of course.
This week - Somewhere between M-F
Very Soon - We should get it out this week, but can we include Saturday & Sunday?
|
As for NE somewhere on the order of:
Quote:
Next week - Or so & including weekends.
Shortly - Possibly sometime around late next week.
Coming Soon - Shortly + 1 week.
|
*In the most non-committal, disclaimer driven way I'm allowed - helping people to roughly plan upgrade timeslots (or create builds), while avoiding a bunch of "you promised now" comments if a target slips.
