[Framework-Team] Re: [Plone 4] Zope 2.12 status
On Jul 1, 2009, at 8:07 AM, Eric Steele wrote: I completely forgot to ask about your migration progress yesterday during our meeting. Would you mind giving us a quick update on where you stand? Any blockers that we could help you with? My todo list looks something like this: - track down and resolve the remaining 11 test failures in CMFPlone - start testing the other packages (and probably merging some more things for them) - finish making plone.recipe.zope2instance work for eggified zopes - sort out PloneFolder situation (it can probably go but I need to confirm that) - sort out actions API change (Hanno changed the way you fetch an action category on trunk; I haven't had a chance to look closely and figure out what the risks are yet) - sort out action icon changes - sort out plone.app.upgrades - sort out GRUF/PAS changes (on trunk Hanno removed the GRUF dependency and moved the tools to PlonePAS...I need to figure out how risky this is) - sort out KSS (actually this is already partially sorted out, I'm just waiting on commit access to codespeak) - sort out use of Globals and other deprecation warnings - sort out javascript stuff (on trunk Martijn and Roel moved this to plone.app.javascript, I need to look more closely) - sort out image traversal stuff / linkintegrity (image scales are now found via an IPublishTraverse adapter rather than __bobo_traverse__, which doesn't work during non-publish traversal, so linkintegrity fails to detect that images are linked in a document) - make sure release notes, etc, are up to date Assistance welcome! David Glick Web Developer ONE/Northwest New tools and strategies for engaging people in protecting the environment http://www.onenw.org davidgl...@onenw.org work: (206) 286-1235 x32 mobile: (206) 679-3833 Subscribe to ONEList, our email newsletter! Practical advice for effective online engagement http://www.onenw.org/full_signup ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: [Plone 4] Zope 2.12 status
On Jul 1, 2009, at 12:13 PM, Hanno Schlichting wrote: As a general comment, it might be that selectively trying to backport my stuff won't necessarily be the quickest way forward anymore. Especially ones you hit stuff I did later on, it all moves to dependency reduction and speedups, which aren't required to get the stuff running on Zope 2.12. Working from the unittests / TTW-testing until stuff works is another way to do it. Yep, I've already shifted mostly into this mode. - sort out PloneFolder situation (it can probably go but I need to confirm that) I think I responded to that already... it can go, as its only used indirectly by the temporary folder from portal factory and some tests. Or you let it stay. It doesn't matter much, as it's so little. Yeah, you did, I just haven't had a chance to deal with it yet. - sort out actions API change (Hanno changed the way you fetch an action category on trunk; I haven't had a chance to look closely and figure out what the risks are yet) I'd stay away from those. There's quite a number of evolutionary changes made over time. The end result as seen today on trunk is nowhere near what I'd consider to be finished. This is really a separate change. Even in its minimal version it requires backwards-incompatible API changes, that currently aren't documented. It should also be a more conscious choice to break API compatibility with the CMF actions API, which I did here implicitly. Yep. It's on the todo list because I merged some of this before I understood its implications, and I have to take it back out. - sort out GRUF/PAS changes (on trunk Hanno removed the GRUF dependency and moved the tools to PlonePAS...I need to figure out how risky this is) Merging all the functionality into one place and getting rid of the GRUF package should be fairly save. It just needs BBB imports in the old locations in CMFPlone, so that persistent versions continue to work. We could either live with those BBB imports in place or write a migration, which updates the persistent stuff to use the new canonical import location. Or you don't touch any of this, as it's not strictly required to get stuff running. Yep. Thanks for this info. - sort out use of Globals and other deprecation warnings That should all be fairly simple and just time consuming. It's a job for grep after InitializeClass for the most part. Yep. - sort out javascript stuff (on trunk Martijn and Roel moved this to plone.app.javascript, I need to look more closely) The p.a.javascript stuff also includes rewriting some of that JS to jQuery and making a number of other changes. I'd just ignore all of that and continue to keep the JS files as found in Plone 3.x. Yeah, that seems like the safe approach. We should probably at least update to the latest jquery though. - sort out image traversal stuff / linkintegrity (image scales are now found via an IPublishTraverse adapter rather than __bobo_traverse__, which doesn't work during non-publish traversal, so linkintegrity fails to detect that images are linked in a document) Huh? I thought that change was only part of Archetypes trunk and not in the scope of Plone 4. I haven't given a lot of attention to Archetypes yet. We can (and probably should) exclude that change. David Glick Web Developer ONE/Northwest New tools and strategies for engaging people in protecting the environment http://www.onenw.org davidgl...@onenw.org work: (206) 286-1235 x32 mobile: (206) 679-3833 Subscribe to ONEList, our email newsletter! Practical advice for effective online engagement http://www.onenw.org/full_signup ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[PLIP-Advisories] Re: [Plone] #9324: Use Amberjack to offer guided help for first-time users
#9324: Use Amberjack to offer guided help for first-time users ---+ Reporter: limi |Owner: Type: PLIP | Status: new Priority: n/a|Milestone: 4.0 Component: Documentation | Resolution: Keywords: | ---+ Comment(by limi): Replying to [comment:17 calvinhp]: FWT Vote: -0, but I could be swayed to a +1 if we were to only include this functionality as an extended install option that was off by default in the standard installers a la the firefox installers option to install the developer plugins. That's what I meant by optional install, sorry if I was unclear on that. -- Ticket URL: http://dev.plone.org/plone/ticket/9324#comment:19 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [Framework-Team] Re: [Plone 4] Zope 2.12 status
On Jul 1, 2009, at 9:22 PM, David Glick wrote: On Jul 1, 2009, at 12:13 PM, Hanno Schlichting wrote: - sort out image traversal stuff / linkintegrity (image scales are now found via an IPublishTraverse adapter rather than __bobo_traverse__, which doesn't work during non-publish traversal, so linkintegrity fails to detect that images are linked in a document) Huh? I thought that change was only part of Archetypes trunk and not in the scope of Plone 4. I haven't given a lot of attention to Archetypes yet. We can (and probably should) exclude that change. otoh, `plone.app.imaging` also introduces that adapter, and as it was mainly created as a support package for adding image support to `plone.app.blob` (did you think anyone wanted those configurable image scales? :)). that's because the latter overrides the original adapter with an implementation based on zodb blobs. so i'm gonna argue for it's inclusion into plone 4, thereby bringing back the `IPublishTraverse` adapter. of course, limi simply converted that old PSPS ticket (#7822) into a PLIP and i didn't think of adding a reference to that dependency, so the fwt will have a point in turning this down. i should mention, though, that not being able to rely on `plone.app.imaging` would set back image support quite a bit and thereby reduce the chances of wrapping up blob support in time. also, i think the configurable image scales have been a popular request by some (b1 had 500+ downloads in 1.5 month ;)). anyway, and stopping the shameless advertising here, i think back- porting the traversal adapter might make sense, and since both `plone.app.imaging` (being a potential candidate needing this) and `plone.app.linkintegrity` happen to be packages i'm familiar with, i'd volunteer to help fixing the issue. how's that? :) cheers, andi -- zeidler it consulting - http://zitc.de/ - i...@zitc.de friedelstraße 31 - 12047 berlin - telefon +49 30 25563779 pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/ plone 3.2.2 released! -- http://plone.org/products/plone/ PGP.sig Description: This is a digitally signed message part ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
