Re: anyone gone to 5.0.10 or 11 in production?

Good advice, and I've passed it on. One thing we have now noticed affects us as Canadians.

Since there is no English (Canada) Language or localization, and since bug 30941 said the Calendar should be 24-hours, bingo, we have a 24-hour calendar display window! I've added to the bug (which is marked fixed) and hopefully that will be picked up. I've asked for:

Any chance of:
 1 A language called: English (Can)
 2 The option to set the time to either 24-hour or 12-hour, 
 3 The preference to set the start and end time of your calendar view 

If you solve 3, I'll take 2 off the table :-)

If any Canadians want to vote for this, I'd appreciate it eh! I know, I know....Gerrit

Gerrit Bos
Lead, Communication and Collaboration Cluster, CCS
Email: gbos@uoguelph.ca
Ph: (519) 824-4120 Ext. 53489

----- "Steve Hillman" <hillman@sfu.ca> wrote:
> We've now done the upgrade to 5.0.11 as well with no problems encountered.
>
> ----- "Rich Graves" <rgraves@carleton.edu> wrote:
> >
> > I have been able to avoid/anticipate pretty much all such issues by,
> > *immediately* after each new ZCS release, taking a SAN snapshot of
> > production /opt/zimbra (on our Compellent SAN, this is easy and has
> > essentially no performance overhead on either production or test);
> > upgrading that snapshot in a virtual environment; and performing local
> > QA for several weeks, on real user mailboxes. End result, I think I've
> > been upgrading ZCS more frequently than most of you, and with less
> > user impact. If your infrastructure doesn't let you do that, consider
> > what it would take to get there.
>
> We do this as well - I *highly* encourage it if you have a storage back-end that can take snapshots and turn them into volumes. Using this, we've been able to maintain a "staging" environment that's kept in sync with prod - we typically refresh the staging environment about once a week, although we freeze it while we're testing new upgrades.
>
> We use it not only for testing rollouts of new versions, but also for testing new features, and try out Zimlets. Once a Zimlet is deployed, it's often necessary to stop and restart the mailboxd process if you need to redeploy the Zimlet, so you want to make sure it's working perfectly before you deploy it the first time!
>
> --
> Steve Hillman IT Architect
> hillman@sfu.ca IT Infrastructure
> 778-782-3960 Simon Fraser University
>
>