Important: Release clarifications and updates

I've put a couple of hours into cleaning this up with Alan and Simon, and  
the following mail summarizes what's been done. Mandatory reading. :)

On Tue, 16 Mar 2004 09:33:48 -0600, alan runyan  
<[email protected]> wrote:

> Base Plone - which is just the CMFPlone tarball.
> Plone - which contains the dependencies (listed below).

We need to clarify the word usage here a bit. If we're going to stick with  
what we planned for 2.1, "Plone" refers to Plone-the-Product, i.e. all the  
included bits in the installers/packages. So here are the definitions  
we've agreed on:

DEFINITIONS
-----------

Plone Base -- Just the CMFPlone dir/tarball (only for internal use in the  
installers etc since it doesn't do anything withtout the dependencies)

Plone Core -- The minimal set of dependencies required to run, *including  
the correct CMF version shipping with Plone as the 2.0 tarball  
demonstrates*.

Plone (aka. Plone the Product) -- What ships with the installers and  
packages.

The Linux people are free to create plone-core packages if they see that  
as useful, but the main package should:

- Be called 'Plone' (or 'plone', where appropriate) (not CMFPlone or  
anything else)

- Ship with everything that is defined as PtP, so users get a good  
out-of-the-box experience even on Linux. Example: If I do 'apt-get install  
plone' on my debian box, I expect to get:

- Zope installed

- CMF (from the Plone Core package, this is the only way we can guarantee  
that people are using the correct CMF version corresponding to their Plone  
version)

- All the Products that ship with the installers

If you want to have a minimal install, create an additional install called  
plone-core, which can ship without the additional extras.

I've added this info to the release team area - if anyone disagrees, now's  
the time to speak up. :)

It's in the releas area, here:
http://plone.org/development/teams/release/definitions


TARBALL CHANGES
---------------

Alan updated the tarball to only use released files instead of the CVS  
versions. I did a full diff of the old and new tarball, and the only thing  
this is affected is CMF1.4.3rc1 (which I believe only shipped with the  
Windows installer), and CMFQuickInstaller. No changes to CMFPlone.

Thus, you don't really need to rebuild the installers. The changes are  
unimportant, the main point is that we have to start building installers  
 from released versions, not from CVS. You use Plone Core as your base, and  
add additional packages on top of that.

http://plone.org/development/teams/release/installer

(Would be nice if you fill in the packages that are supposed to be in all  
the installers - ArchGenXML? ZWiki? I don't have the full list, and  
currently the Plone installer for Windows ships with mostly only the Core  
products. The implications of the new strategy won't appear properly until  
the 2.1 release, obviously - so stick with what you have in the installers  
for now.)

SF.NET FILE CATEGORIES
----------------------

To match the strategy outlined above, I've updated the file categories on  
sf.net to look like this:

- base (inactive for now, not sure if we need to use this on SF at all)

- core (the core tarball used for building installers and for People Who  
Want Only The Bare Essentials)

- installers (same as before, contains Plone-the-Product aka. Plone)

- old (the old tarballs from the 'plone' category - in case somebody needs  
them)

WIKI MUST DIE
-------------

As part of the clean-up, I made all the content into normal documents  
instead of Wiki pages. I was getting random ZWiki errors, and decided  
enough was enough. I also know that none of us are particularly fond of  
wikis, so I assumed it was a safe thing to do.

I also created a Folder for the releases - as having all the release  
objects in the main folder won't scale. ;)

Everything is now accessible from:
http://plone.org/development/teams/release

*Please* read through all the documents, so we are all on the same page.  
We need to have this ready for when 2.1 development starts, and I want to  
hand Andy a nicer package than what we've had so far. :)


SUMMARY
-------

- Release Team area updated:
   http://plone.org/development/teams/release/

- SF.net updated:
   https://sourceforge.net/project/showfiles.php?group_id=47214

- Tarball updated (but no need to rebuild the installers)

- Use Plone Core as the basis for future installers

That should be all. :)

-- 
__________________________________________________________________

  Alexander Limi   ·   Interaction Architect   ·   Plone Solutions

  Development · Training · Support · http://www.plonesolutions.com
__________________________________________________________________

  Plone Co-Founder   ·   http://plone.org   ·   Connecting Content



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