[Zope-CMF] cmf-tests - OK: 4
This is the summary for test reports received on the cmf-tests list between 2012-03-20 00:00:00 UTC and 2012-03-21 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
On Mar 20, 2012, at 23:25 , Jens Vagelpohl wrote: > > On Mar 20, 2012, at 16:14 , Charlie Clark wrote: > >> Hi, >> >> 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? If that is the case then I think we're good to go with 2.3. > > > If there are no objections I could run through the packages and create 2.3.0 > betas later this week or this coming weekend. The beta eggs are released now. 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
Am 21.03.2012, 16:47 Uhr, schrieb Jens Vagelpohl : If we keep piling up tasks that are too big to be tackled in a small amount of time as part of the release process we'll never get anything released. I would classify both these items as "nice to have, but not on the critical path". True. I've done a *very* basic port of the docs to ReST so that Sphinx will at least generate stuff. This has been done by copying the exiting STX files and renaming them. Should they be moved instead to preserve the history? 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
On Mar 21, 2012, at 15:55 , Charlie Clark wrote: > Am 21.03.2012, 00:36 Uhr, schrieb Tres Seaver : > >> Sounds good. We should review the code for any stuff >> deprecated-and-promised-to-be-remove-in-2.3 before releasing a beta. > > 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. > > 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. If we keep piling up tasks that are too big to be tackled in a small amount of time as part of the release process we'll never get anything released. I would classify both these items as "nice to have, but not on the critical path". 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
Am 21.03.2012, 00:36 Uhr, schrieb Tres Seaver : Sounds good. We should review the code for any stuff deprecated-and-promised-to-be-remove-in-2.3 before releasing a beta. 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. 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. 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
