Re: Re: Mac OS X Installer Progress 20050911-1700

On 12-Sep-05, at 5:45 PM, Andy McKay wrote:


> Alexander Limi wrote:
>
>
>> On Mon, 12 Sep 2005 23:01:00 +0200, Andy McKay   
>> <andy-/awGbKECNgO/3pe1ocb+swC/[email protected]> wrote:
>>
>>
>>> +1, auto-updating is not a good idea, especially if the update  
>>> process  is not simple eg Plone 2 to Plone 2.1.
>>>
>>
>> I'm not talking about running the actual migration script, but I  
>> would at  least expect my instance to be using the new 2.1 code.
>>
>
> The file system code should be 2.1. The database should be running  
> 2.0.x and need the migration running.
>
> Are you saying the file system code is not 2.1? In which case I  
> agree ;)
>

The policy for the Sites folder in the Plone for Mac OS X installer  
has always been that the Sites folder belongs to the user, not the  
installer.  The installer will not touch their instances.  (I think  
there's been one exception around the time of transitioning from Zope  
2.7 RC2 to Zope 2.7-final, to work around a serious bug)  The process  
of upgrading a production Plone environment from one version to  
another is never assumed to be straightforward and bulletproof enough  
to warrant an automated process, but we can help with the grunt work.

When they do the initial installation, it creates a "Default" site  
(ie: Zope instance with a Plone site in the root of the ZODB) for  
them.  If an installer is run and upgrades an existing installation,  
and it finds the Sites folder in /Applications/Plone2, it does not  
touch that folder.  If it doesn't find the Sites folder, it creates  
it and the first instance_home, at /Applications/Plone2/Sites/Default.

Remember, the Plone for Mac OS X environment is designed to support  
multiple Zope instances.

The installer provides an upgrade script (and instructions for its  
use) that a user can run to upgrade *an* instance to Plone 2.1  
products.  It replaces the products with the ones in Plone Core 2.1  
and updates their instance's Zope configuration to use the new  
software stack (Python 2.3.5 and Zope 2.7.7, since Plone 2.1 does not  
work on the old stack, Python 2.3.4 and Zope 2.7.3).  The  
instructions tell the user to start their instance and run the  
portal_migration script after running the upgrade script.

The supplied documentation is very clear that if a user wants a fresh  
Plone 2.1 site after upgrading they should run the newsite command.

Jim




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf