Re: IMPORTANT - READ IT

On Tuesday, March 16, 2004, at 07:33  AM, alan runyan wrote:

> So..  it seems there is no firm guidelines for installers.
> Here is how it works now, someone put this in the docs.
>
> Simon made this:
> http://plone.org/development/teams/release/notes/DistributionContent
>
> Someone in charge of the Release team please flesh out the info.
> Also What is Jello? (Version number) What is MuslimGauze (version
> number)?
>
> He will create a script that you can run and will fetch everything from
> http instead of having to go grab tarballs or cvs entries.
>
> I will re-release a tarball, just to make sure everything is perfect.
> And follows consistency.  Simon eisenman will make a script that
> will enable users/package maintainers to run it and get all the  
> available
> packages for their platform (as advertised).
>
> Base Plone - which is just the CMFPlone tarball.
> Plone - which contains the dependencies (listed below).
>
> I did the work, someone needs to update the documentation.
> Also this completely neglects the idea of wx, XController
> and other CMF/Plone Add-ons, such as CMFPhotoAlbum.
> These need to be documented on each installer.

[snipped the products that the osx installer is using the same version  
of]

> QuickInstallerTool - 1.4 (hooray for not being CMFQuickInstaller)
> http://prdownloads.sourceforge.net/collective/ 
> CMFQuickInstallerTool_1.4.tgz?download

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

> 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.

> 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.

> 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.

> BTreeFolder - BTreeFolder2-1.0+
> found only in CVS

BTreeFolder2-0.5.0+ was in the Plone 2.0 tarball.

> 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'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.

Cheers,

Jim

--
Jim Roepcke
Tyrell Software Corp  <http://www.tyrell.com/>



-------------------------------------------------------
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