[plumi-discuss] workplan for Plumi (ver. 3)

andy nicholson andy at engagemedia.org
Tue Sep 23 19:08:00 EST 2008


Hi

Steps 1, and 2, are now mostly done - as you would of seen Plumi
0.2.1-final is released. We have decided to work on Plumi 0.2.2 to
include UI enchancements for the current plone 2.5.5 env. but not to
waste too much time on this.

http://plumi.org/report/3  [ see milestone 0.2.2 ]


Ive updated the plumi buildout SVN trunk to use this new version, and
the latest zope 2.9.9, check below in step 2 for details.

andy
----

PLUMI WORK PLAN
===============
23/09/2008

1) plumi 0.2.1 release in new tarball package on plone.org

*	indytube branch, with new dev for mkdirs fix + mencoder cmd line fix +
others

	new branch :
https://svn.engagemedia.org/project/indytube/branches/plumi-0.2.1/ 
		     copied from the last tag we used for plumi-0.2-final.
		     see http://plumi.org/changeset/347/indytube
		
		The *trunk* of indytube contains the current egg-ified version of
indytube , designed to work 
		via XMLRPC with a queue system - called ZopeTube :
http://plumi.org/browser/ZopeTube.
		This is still in pre-alpha.
	
	changelogs for bugfixes:
			http://plumi.org/changeset/348/indytube
			http://plumi.org/changeset/349/indytube
			http://plumi.org/changeset/350/indytube
			http://plumi.org/changeset/351/indytube
			http://plumi.org/changeset/352/indytube
			http://plumi.org/changeset/353/indytube
	new tag :
		https://svn.engagemedia.org/project/indytube/tags/plumi-0.2.1-0
		
	
* ATVideo branch 'plumi-0.2.1-rc1' with RSS1 feed bugfix :
		https://svn.plone.org/svn/collective/ATVideo/branches/plumi-0.2.1-rc1/
		http://dev.plone.org/collective/changeset/72078

	changelogs:
		http://dev.plone.org/collective/changeset/72079		
		http://dev.plone.org/collective/changeset/72153
		http://dev.plone.org/collective/changeset/72158

		( http://dev.plone.org/collective/log/ATVideo )

	latest tag: 		
		https://svn.plone.org/svn/collective/ATVideo/tags/plumi-0.2.1-rc3


* New version of PlumiSkin 

	http://dev.plone.org/collective/changeset/72143

	https://svn.plone.org/svn/collective/PlumiSkin/tags/plumi-0.2.1-rc1

* make new Plumi branch 0.2.1 

	new branch:
https://svn.plone.org/svn/collective/Plumi/branches/plumi-0.2.1
	
	update EXTERNALS.txt to match those new tags above.
        Updated Products via svn externals (EXTERNALS.txt) :
		* ExternalStorage - update to using new svn url
https://svn.plone.org/svn/collective/Products.ExternalStorage/trunk/Products/ExternalStorage/
			see :
https://svn.plone.org/svn/collective/Products.ExternalStorage/trunk/Products/ExternalStorage/ChangeLog

		* ATVocabularyManager - updated to 1.4.2 from 1.4rc1
			see :
http://svn.plone.org/svn/archetypes/ATVocabularyManager/tags/1.4.2/HISTORY.txt

		* fatsyndication/basesyndication new svn URLs


	for changelogs see: http://dev.plone.org/collective/log/Plumi

* update CHANGELOG etc


https://svn.plone.org/svn/collective/Plumi/branches/plumi-0.2.1/CHANGELOG.txt


* tag plumi-0.2.1-final

	https://svn.plone.org/svn/collective/Plumi/tags/plumi-0.2.1-final/			

*        Tests::
		upgraded demo.plumi.org to plumi 0.2.1-final -- see
http://demo.plumi.org/
		upgraded engagemedia.org to plumi 0.2.1-final	-- see
http://www.engagemedia.org/


* release plumi 0.2.1-final tarball on plone.org

	http://plone.org/products/plumi/releases/0.2.1-final


2) Update plumi-0.2-buildout trunk -
http://plumi.org/browser/plumi-buildout-plone2.5

	*       pointer to new plumi-0.2.1-final tarball, as above.

	*   	update to Zope-2.9.9 

		see -- http://plumi.org/changeset/361/plumi-buildout-plone2.5

* 	Tag a plumi-0.2-1-final release


https://svn.engagemedia.org/project/plumi-buildout-plone2.5/tags/plumi-0.2.1-final
	

--------- TODO below -----------------------------------

*	JSON migrator included via SVN recipe

*      (possibly PloneFlashUpload) .. other eggs/oldstyle products we
want.

* 	tag plumi-0.2-buildout TRUNK, with plumi-0.2.1-export


*	release new plumi-0.2-buildout , with explanation , that the new
buildout incorporates the plumi-0.2.1 tarball
plus extra products pulled in via buildout process, incl. the JSON
migrator, with a view to upgrading to plumi 0.3 / plone 3.x , and the
buildout process itself.


3) plumi 0.3 and plone 3 work

* Current work for this is on the trunk of Plumi

	https://svn.plone.org/svn/collective/Plumi/trunk

*	initial plone 3 compatiable system.
		blob based content type with same view templates.

* 	migration from plumi 0.2.x systems -- import / export xml steps.
	
		possible approach::		
			first migration to atvideo style systems
			second to blob fields
			custom scripts to convert from atvideo-plumi0.2.x to plumi 0.3 + blob
field with JSON migrator

*	then tickets from plumi trac.

.. eventually
* update CHANGELOG etc
* release plumi 0.3 tarball on plone.org
 

---------------------------------


JSON migrator plan

http://mxm-mad-science.blogspot.com/search/label/plone
(love that url name)


Need to migrate:
	ATEngageVideo files
	Members + their folders + content.
	News
	Events
	Callouts
	SimpleVocabulary
	SimpleVocabularyTerm
	SmartFolders -- the smart folders of content (topics, genres,
countries)
	ATEngageVideoFolders
	Discussion Items -- coments
   	File
    	Images

Dont need to migrate:

	Tag cloud


-- 
Andy Nicholson

http://wiki.infiniterecursion.com.au/wiki/ContactDetails
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.plumi.org/pipermail/discuss/attachments/20080923/0199bcab/attachment.pgp>


More information about the Discuss mailing list