[CalendarServer-users] Refreshing a running Calendar Server instance with latest build

[Scott Buchanan]

When you say release branches the only one I see is the 1.3.  Do you  
also mean the prop-?
On May 24, 2008, at 8:53 AM, Cyrus Daboo wrote:

> Be careful about usingvtrunk right now as we are doing a lot of work
> there and some things may break. Use one of the latest Release
> branches instead  for any production system.
>
> There should not be any issues with data migration. But bare in mind
> migration is only one way so you won't be able to downgrade to an
> older rev after running the newer one. So you may want to take a
> snapshot of your data directory before the upgrade.
>
> -- 
> Cyrus Daboo
> (Tapped out on my iPhone)
>
>
> On May 23, 2008, at 5:06 PM, Name Withheld <bookondesk at gmail.com>  
> wrote:
>
>> Newbie alert  -- please be gentle.
>>
>> I have a home Calendar Server instance that's been happily running
>> on Leopard since November 2007, serving three Leopard iCal
>> clients.   For the most part it's been running fine but there have
>> been some odd quirks in calendar event creation lately.  It strikes
>> me that it would be prudent to refresh this with the latest build.
>>
>> Here's what I plan to do:
>> Shut down the existing instance
>> Back up my master CalDav directory and all the current calendar data
>> Execute this Subversion command to obtain the latest build
>> Recompile and restart the instance
>> Is this a valid approach?  Do I need to worry about any XML metadata
>> changes between the existing calendar data and the current build as
>> of May 23?
>>
>> Regards,
>> Steven
>> _______________________________________________
>> calendarserver-users mailing list
>> calendarserver-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
> _______________________________________________
> calendarserver-users mailing list
> calendarserver-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users