-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all,
Ive updated http://plumi.org/wiki/Plumi3.0WorkPlan to reflect the just tagged beta1 release of the plumi 3.0 buildout! :-) see http://latest-a.plumi.org/ to test this new release. The database comes (somewhat recently) from http://demo.plumi.org/ running plumi 0.2.3-final [ http://testing.plumi.org is running plumi 0.2.4-rc2 ] File any bugs related to _migration issues_ against the plumi 3.0-beta milestone on the trac Any bugs about functionality go into the plumi 3.0-final milestone - -- I think Ive finished the last of the migration issues Ive known about , the last ones being the comments, and custom licenses. Eg here are some good examples of checking for all aspects of the video content type are being ported correctly. http://latest-a.plumi.org/Members/jonair/videos/salsla02.wmv/view http://demo.plumi.org/Members/jonair/videos/salsla02.wmv/view http://latest-a.plumi.org/Members/andenator/videos/itravellp.mp4/view http://demo.plumi.org/Members/andenator/videos/itravellp.mp4/view - -- In general we need to check these as anonymous and as an admin, to see different effect when logged in or not ** This reveals actually, that it looks like nobody but admin can see comments, even published ones ? We need to confirm this. It may just be configuration issue with the new version of quintagroup.plonecomments just added as an egg into the buildout recently.. Things to check for are custom license fields, comments , and workflow of comments, and nesting of threads of comments, if the international characters sets are rendering correctly, etc We need to double check everything to do with the members is being ported - their profile , their content etc. Also we need to double check all other valuable content types are being exported - the only one i know of that is missing is Favourites. - -- Ive released new versions of all plumi.* eggs to pypi too - http://pypi.python.org/pypi?%3Aaction=search&term=plumi&submit=search in preparation for when we mark the versions of the eggs to use, in the plumi 3.0-final buildout. - -- We can release betaX releases until the beta milestone bugs are squashed, after which we can release RCs until the 3.0-final milestone is done.. I will be away for 3 weeks, starting next Tuesday, that should give some time to test the bugs in migration and general functionality. I will get onto that , when I get back , with a view to doing the RC / final release before the plone conference/ plone video sprint. see youz later andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqf1eUACgkQQw7kQoXiO3WySACfWx79bdveEN+JhCYI4XpAT8t4 UTAAoJ9iZ+7dSVwL8Si2pT8fnEyRzfIX =u1UA -----END PGP SIGNATURE----- _______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
