I've just noticed that one of our favourite bugs has been fixed and a number of files changed.
Eagerly I rushed to the CVS to take a look at the code (I'm currently using the latest version of the main branch). Imagine my disappointment to find that the affected files had not actually made it to cvs yet!
I'm guessing there's some sort of internal parallel SCM system. Could you please explain the source control process a bit, and let me know how and when the CVS is likely to catch up with what the bug report emails say has been fixed. I'm just a little confused as to how the CVS tree is maintained at the moment.
CVS is a mirrored slave off our internal source control of record. It should be on a ~10-15min delay but at times it's farther behind. What is the exact bug number your looking at and a file or two you think is missing?
The notification I received is below, with bug number and affected files.
------- Additional Comments From firstname.lastname@example.org 2006-06-21 20:08 -------
Change 27415 by cdamon@cdamon on 2006/06/21 18:07:59 *pending*
Bug: 4361, 7452
Remember checked calendars. Checking/unchecking
a calendar triggers a request that saves the state on
the server. On startup, only checked calendars are
Affected files ...
... //depot/main/ZimbraWebClient/WebRoot/js/zimbra/csfe/ZmBatchCommand.js#4 edit
... //depot/main/ZimbraWebClient/WebRoot/js/zimbraMail/calendar/controller/ZmCalViewController.js#148 edit
... //depot/main/ZimbraWebClient/WebRoot/js/zimbraMail/share/controller/ZmCalendarTreeController.js#31 edit
... //depot/main/ZimbraWebClient/WebRoot/js/zimbraMail/share/model/ZmCalendar.js#26 edit
... //depot/main/ZimbraWebClient/WebRoot/js/zimbraMail/share/model/ZmOrganizer.js#70 edit
... //depot/main/ZimbraWebClient/WebRoot/js/zimbraMail/share/model/ZmSearch.js#45 edit
Thanks.. I'll take a look.