hey,
The second tagged alpha release of the plumi 3.0 buildout is out !
and yes, we changed the version number scheme - see here :
http://blog.plumi.org/2009/07/23/new-version-numbering-system/
Plumi 3.0 will be released using the same procedure as Plone 3.2 - that
is, as python eggs, and buildouts not tarballs of product code. [*]
The tagged buildout SVN is here :
http://plumi.org/browser/plumi-buildout-plone3/tags/plumi-3.0-alpha2
SVN url :
https://svn.engagemedia.org/project/plumi-buildout-plone3/tags/plumi-3.0-alpha2
We are getting back into the swing of regular releases of Plumi. We
will release alpha versions , until full Plumi 0.2.x functionality is
achieved, and then start on a Beta release cycle - which will include
code/docs for migrating from plumi 0.2.x sites.
Tracker : http://plumi.org/report/3
Plumi 0.3 workplan : http://plumi.org/wiki/Plumi0.3WorkPlan
thanks
andy
[ * ]
"Beginning with Plone 3.2, Plone will be available as a Python package
and via installers. It will no longer be distributed as a tarball of
old-fashioned Zope products. The change to standard Python packaging
will improve dependency handling and make future installations easier.
But, it will require some adjustments for those used to installing via a
tarball of products. The 3.2 installation will also require some slight
changes in the buildout configuration file for those who have already
been using buildout configuration management in the 3.x series."
http://plone.org/products/plone/releases/3.2
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
