[Zope-CMF] cmf-tests - OK: 4
This is the summary for test reports received on the cmf-tests list between 2012-04-02 00:00:00 UTC and 2012-04-03 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received CMF-2.2 Zope-2.12 Python-2.6.6 : Linux CMF-2.2 Zope-2.13 Python-2.6.6 : Linux CMF-trunk Zope-2.13 Python-2.6.6 : Linux CMF-trunk Zope-trunk Python-2.6.6 : Linux Non-OK results -- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Hi Charlie, On Apr 3, 2012, at 14:55 , Charlie Clark wrote: > Am 03.04.2012, 14:11 Uhr, schrieb yuppie : > >> +1 >> Is CMFDefault/help now obsolete? Could it be deleted? > > I guess so. I'm still working on "tidying" up what can loosely be termed as > the narrative documentation. Still in the clean-up phase but should get this > done this week. > > @ Jens will we be able to point the release to a docs page on Zope.org? *If* there's a working Sphinx documentation set under Products.CMFXXX/doc or Products.CMFXXX/docs I can stitch it into the autogenerated documentation at docs.zope.org. > I had a go at autogenerating the api documentation but failed miserably - > lots of empty pages got generated because Sphinx had trouble with import > paths. Does anyone know the appropriate incantations for this? I can take a look over the next few days. jens ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Hi Yuppie, Am 03.04.2012, 14:11 Uhr, schrieb yuppie : +1 Is CMFDefault/help now obsolete? Could it be deleted? I guess so. I'm still working on "tidying" up what can loosely be termed as the narrative documentation. Still in the clean-up phase but should get this done this week. @ Jens will we be able to point the release to a docs page on Zope.org? I had a go at autogenerating the api documentation but failed miserably - lots of empty pages got generated because Sphinx had trouble with import paths. Does anyone know the appropriate incantations for this? Not sure if this would be for 2.3 but I think that CMFCalendar should be rolled into CMFDefault. The main reason being that the default profile for CMFCalendar uses browser views and explicitly requires the CMFDefault skin layer. You then can't use CMFCalendar if you override the default skin layer. Plus, CMFCalendar's functionality is extremely limited and intimately tied to CMFDefault. -1 CMFCalendar is an example add-on. It should be possible to write add-ons like CMFCalendar. So if there are any issues with keeping it in a separate optional package they should be fixed instead of giving up. Okay. I guess the key issue is making working with Zope-3 skins easier. I'd like to have a different CMFDefault profile that did without CMF skins (yes, I do appreciate the irony), ie. the ability to jetison PythonScripts et al. CMFCalendar won't work with that because of the explicit dependency upon the CMF skin layer. Certainly a big enough change not to be in 2.3. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Hi! Charlie Clark wrote: I finally landed my update step for syndication during the PyCon sprints! I thought I had a few more browser views to update to using the EditSettingsForm but on a quick check of the files it seems that this has already been done. Yuppie, I remember that you have commented out some of my views (portal configuration and membership, I think) because of the encoding problem, did you correct them yourself last year and I was simply looking at old source? Working on my tool and member data changes I touched some of your forms. Maybe I fixed all the known issues. But I didn't review all new forms systematically. If that is the case then I think we're good to go with 2.3. No objections. Today I finished the cleanups I wanted to make before new branches are created. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Hi Charlie! Charlie Clark wrote: I suppose we could also migrate the old Zope Help docs to "docs" for Sphinx generation? I know much of the docs are inaccurate and outdated but this might help expose the worst bits which should then be exorcised or at least pruned. +1 Is CMFDefault/help now obsolete? Could it be deleted? Not sure if this would be for 2.3 but I think that CMFCalendar should be rolled into CMFDefault. The main reason being that the default profile for CMFCalendar uses browser views and explicitly requires the CMFDefault skin layer. You then can't use CMFCalendar if you override the default skin layer. Plus, CMFCalendar's functionality is extremely limited and intimately tied to CMFDefault. -1 CMFCalendar is an example add-on. It should be possible to write add-ons like CMFCalendar. So if there are any issues with keeping it in a separate optional package they should be fixed instead of giving up. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
