Re: IMPORTANT - READ IT

> Version 1.5 devel came in the Plone 2.0 tarball, that's what's in the  
> Mac OS X Plone installer.

this why my fuck up.  Simon called me out on it.  I fixed it.  This is  
what you see.

>> GroupUserFolder - 2.0 (2.0a is on the version.txt)
>> http://prdownloads.sourceforge.net/collective/GroupUserFolder 
>> -2.0.tar.gz?download
>
> The version in the tarball (and thus the Mac OS X Plone installer) is  
> 2.0 and the differences are insignificant... just a couple less empty  
> directories.  Faced with the decision of whether to use the GRUF 2.0  
> tarball or the GRUF 2.0 in the Plone 2.0 tarball, I chose the latter.

its your installer.

>> PlacelessTranslationService - 1.0fork-rc3
>> http://prdownloads.sourceforge.net/collective/ 
>> PlacelessTranslationService-1.0fork-rc3.tar.gz?download
>
> UNRELEASED/CVS was in the Plone 2.0 tarball.

yes.. again me working from CVS

>> ExternalEditor - 0.7.1
>> http://zope.org/Members/Caseman/ExternalEditor/0.7/ExternalEditor 
>> -0.7.tgz
>
> It says it's 0.7.1 on the web page but it's actually 0.7 in the  
> version.txt.

ok -

>> BTreeFolder - BTreeFolder2-1.0+
>> found only in CVS
>
> BTreeFolder2-0.5.0+ was in the Plone 2.0 tarball.

I think the only change is a whitespace change.

>> CMFActionIcons - 0.9
>> http://zope.org/Members/tseaver/CMFActionIcons
>
> There's no version.txt in the CMFActionIcons from the Plone 2.0  
> tarball.
>
>> PloneErrorReporting
>> http://prdownloads.sourceforge.net/collective/ 
>> PloneErrorReporting.0_1.tar.gz?download
>
> If we change versions of dependencies, we need another RC or at least  
> more time for testing.  The versions in the original Plone 2.0 tarball  
> are the versions that everyone has been testing with, these are the  
> ones that are known to work, and these are the ones that were released  
> for 2.0 and are already in (some) installers.

I agree.  This means we either should cut new releases of  
CMFQuickinstaller (which people have been
complaining about InvalidObjectReferences) - remember Andy made the Hot  
loading of products in QuickInstaller.
I should not have been fetching from HEAD.

I'm opposed to making another RC - the changes are insignificant.  Limi  
did a diff and pasted it to the list.  Its not
a big change.  there are some CMF problems that have been fixed.  We  
can get a 1.4.3 out for a Plone 2.0.1
I would expect Plone 2.0.1 very shortly after Plone 2.0 -- all of this  
is dependent on andy.

> I'm all for getting sync'd up between platforms for installer/package  
> releases.  IMO, minor changes to the products can go into the 2.0.1  
> installer, and we can start using the Products-dir-building-script at  
> that time and moving forward... assuming that the script doesn't get  
> changed a few hours after I finish an installer and am told I need to  
> re-run it and make a new installer.

I think everything has been laid out pretty concisely.  If there are  
problems they should be raised.
Maybe I'm being stupid but I dont see the enormous problem.  fetch the  
tarball - build installer with it.
Simon will have RPMS hopefully out tomorrow.

NOTE: Its not like we change Plone from under you guys.  We are  
synchronizing all the dependencies.
Everything is up for it - sure.  We did it, for Plone 2.0 instead of  
Plone 2.0.1.  I appreciate the lack of
abuse (which I did expect ;-) from everyone.  Lets try to roll these  
things out.

alan



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click