Re: [Zope-CMF] CMF 1.5.3 beta?
Alright, it's out now. I probably spent 90% of the last two hours fighting zope.org which was near-unresponsive... Anyway, since this is a beta the usual precautions apply: - No non-critical-bugfix checkins on the CMF 1.5 branch until CMF 1.5.3 final is out - Please help test the release, especially the changes shown below that have flown in since the last release. CMF 1.5.3 will be the release Plone 2.1 final is based on (if nothing bad happens in the meantime), it will see very widespread use, so good quality control is important. I am hoping we can have a quick beta cycle with just this beta release. Please test! ;) --- Bugs Fixed - Changed the INSTALL_SVN instructions to conform to the new branch and tag naming scheme instituted for the subversion repository. - Apply an interim fix for slow pathwalking implementation in development mode on Windows (http://www.zope.org/Collectors/ CMF/367) Note that a better fix would be to leverage pywin32 APIs for file / directory monitoring. - FSObject.manage_doCustomize() was broken for folderish objects on Zope 2.8 because manage_permission requires a context to work. (see http://www.zope.org/Collectors/CMF/368) - CMFCore/FSPropertiesObject and CMFCore/FSMetadata: Removed a wrongly inserted DeprecationWarning in the FSPropertiesObject class and put it into the FSMetadata class. We are not deprecating ".props" files, but ".properties" and ".security". - Change CVS checkout documentation to their equivalent Subversion instructions - In CMFSetup, make sure to give special treatment to both CVS and .svn folders where this is necessary (e.g. to implicitly skip them when importing profiles) - Made sure FSDVTest always deletes its temporary folder on tearDown. (http://www.zope.org/Collectors/CMF/106) - Fix DefaultWorkflowDefinition bug on isActionSupported() for the keywargs support to reflect DCWorkflowDefinition changes. Add a test case for this definition as well. Others - CMFCatalogAware: reindexObjectSecurity() now always reindexes the catalog objects without changing their catalog uid. This is useful for third-party code that indexes objects with special uids. - jens ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] CMF 1.5.3-beta released
The CMF developer community and Zope Corporation are pleased to announce the release of version 1.5.3-beta of the Zope Content Management Framework (CMF). This release is intended for testing purposes only; we do not recommend deploying it to production servers. The final release of version 1.5.3 is expected to land within about 10 days. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. As packaged, the CMF generates a site much like the Zope.org site. The CMF is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? Download it from http://zope.org/Products/CMF/CMF-1.5.3-beta Points of interest include: - "Windows ZIP file", http://zope.org/Products/CMF/CMF-1.5.3-beta/CMF-1.5.3-beta.zip - "Unix tar/gzip archive", http://zope.org/Products/CMF/CMF-1.5.3-beta/CMF-1.5.3- beta.tar.gz . - "Release notes", http://zope.org/Products/CMF/CMF-1.5.3-beta/README.txt - "Change history", http://zope.org/Products/CMF/CMF-1.5.3-beta/CHANGES.txt - "Installation instructions", http://zope.org/Products/CMF/CMF-1.5.3-beta/INSTALL.txt Where do I go to learn more? The CMF mailing list ([EMAIL PROTECTED]) has many participants who are active in supporting the CMF. ...to report bugs? The "CMF Collector":http://zope.org/Collectors/CMF is the place to report bugs (please search for existing reports of your issue first!) - Jens Vagelpohl [EMAIL PROTECTED] ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CMF 1.5.3 beta?
Jens Vagelpohl <[EMAIL PROTECTED]> wrote: > Florent: Quick heads-up to me when you're done with your changes, > please. Ok I'm done I think. Heads up for Plone devs (but we were discussing it on #plone): The change I made impacts the signature of CatalogTool.reindexObject, which until recently Plone was overloading. http://svn.zope.org/CMF/branches/1.5/CMFCore/CatalogTool.py?rev=37626&view=rev Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CMF 1.5.3 beta?
Alec Mitchell <[EMAIL PROTECTED]> wrote: > On Monday 01 August 2005 06:55 am, Florent Guillaume wrote: > > However I'd like to urge the "Plone guys" (95% of which don't bother to > > read or post in this list) to move their collective butts and actually > > implement forward-compatibility in Plone itself rather that, once more, > > tying the release of a base software to their own schedule. > > I'm on here too, though pretty quiet. I've even been subscribed here longer > than I have been subscribed to plone-devel. > > As stated, the only important issues are minor bugfixes in CMF 1.5. We'd be > OK without them, but everybody would be better off with them. Maintaining > our own monkeypatch set with every svn fix to CMF is a bit untenable. Agreed. Sorry, I didn't mean to sound so harsh. I was just trying to advocate a technical solution which, in my experience, makes it quite easy to manage unsynchronized releases. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CMF 1.5.3 beta?
On Monday 01 August 2005 06:55 am, Florent Guillaume wrote: > However I'd like to urge the "Plone guys" (95% of which don't bother to > read or post in this list) to move their collective butts and actually > implement forward-compatibility in Plone itself rather that, once more, > tying the release of a base software to their own schedule. I'm on here too, though pretty quiet. I've even been subscribed here longer than I have been subscribed to plone-devel. As stated, the only important issues are minor bugfixes in CMF 1.5. We'd be OK without them, but everybody would be better off with them. Maintaining our own monkeypatch set with every svn fix to CMF is a bit untenable. Alec ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CMF 1.5.3 beta?
If we have a go for the beta I suggest cutting the tag and publishing the release tomorrow morning, about 9am british time. That way zope.org won't have traffic from the Americas, making it marginally more responsive ;) Great, thanks! I am planning to release Plone 2.1 final in 2 weeks. Would be convenient to have CMF 1.5.3 final by then. Yes, if we can keep the beta cycle short and the changeset manageable. With everyone helping out testing the changed bits that came in since 1.5.2 and no big isssues arising a single beta can be sufficient. I'm here, I'm here . If you'd dis Plone a little less I am sure more of us would chime in more often ;-) Don't tell me you're scared of certain peoples' personal opinion... :P jens ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CMF 1.5.3 beta?
On 1. Aug 2005, at 16:24, Jens Vagelpohl wrote: If we have a go for the beta I suggest cutting the tag and publishing the release tomorrow morning, about 9am british time. That way zope.org won't have traffic from the Americas, making it marginally more responsive ;) Great, thanks! I am planning to release Plone 2.1 final in 2 weeks. Would be convenient to have CMF 1.5.3 final by then. jens P.S.: I too think that more participation from the main "consumers", the Plone developers, is sorely needed on this list. I'm here, I'm here . If you'd dis Plone a little less I am sure more of us would chime in more often ;-) Stefan -- Anything that happens, happens. --Douglas Adams ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CMF 1.5.3 beta?
I learned this morning that the Plone 2.1 RC went out (I am told) with CMF 1.5.2. The really crucial fix for them (making the pathwalk in DirectoryView less painfully slow) only really affects people running from SVN checkouts; OTOH, SVN is the only way to get the RC. I assume this means they want to have 1.5.3-final for the pathwalk fix so they can make the Plone 2.1-final release depend on it. Sounds reasonable. Florent: Quick heads-up to me when you're done with your changes, please. If we have a go for the beta I suggest cutting the tag and publishing the release tomorrow morning, about 9am british time. That way zope.org won't have traffic from the Americas, making it marginally more responsive ;) jens P.S.: I too think that more participation from the main "consumers", the Plone developers, is sorely needed on this list. ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CMF 1.5.3 beta?
On 1 Aug 2005, at 16:04, Tres Seaver wrote: We have been doing it in CPS for a while, in a "CPSCompat" product. It's very easy, this is python, we can monkey-patch everything we need. The problem with that approach is that it introduces the risk that bugfixes never make it back to the underlying product, because nobody has the incentive (beyond good intentions) to land them. Of course, nobody would actually succumb to that temptation. My policy is to include in CPSCompat only code that has alreay been checked in to the CMF 1.5 branch or (or Zope 2.8 branch), and excatly that code (no additional patches). This avoids the problem you mention, because I know the code I need will be in the next minor release, so everything gets to be maintained properly. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
RE: [Zope-CMF] CMF 1.5.3 beta?
Tres, Is there anything needed on our end to get them "cleared for access"? I can assist moving that along if so. Andrew -- Zope Managed Hosting Software Engineer Zope Corporation (540) 361-1700 > -Original Message- > From: [EMAIL PROTECTED] [mailto:zope-cmf- > [EMAIL PROTECTED] On Behalf Of Tres Seaver > Sent: Monday, August 01, 2005 10:04 AM > To: Florent Guillaume > Cc: [EMAIL PROTECTED] > Subject: Re: [Zope-CMF] CMF 1.5.3 beta? > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Florent Guillaume wrote: > > Tres Seaver <[EMAIL PROTECTED]> wrote: > > > >>Because the Plone guys are trying to release a 2.1RC at OSCOM, and > >>because it would be sensible for them to use the fixes made since 1.5.2 > >>to the 1.5 branch, I'm wondering if we should be tagging a beta of > 1.5.3. > >> > >>Any objections? I may or may not get around to making a release for it. > > > > No objection. I'll slip in a few changes to reindexObjectSecurity today > > too probably. > > > > However I'd like to urge the "Plone guys" (95% of which don't bother to > > read or post in this list) to move their collective butts and actually > > implement forward-compatibility in Plone itself rather that, once more, > > tying the release of a base software to their own schedule. > > I've been working on getting more of them focused on the maintenance of > CMF: Andy McKay, Geoff Davis, and Alec Mitchell each have fixes they > want to land as soon as they get cleared for SVN access. > > > We have been doing it in CPS for a while, in a "CPSCompat" product. It's > > very easy, this is python, we can monkey-patch everything we need. > > The problem with that approach is that it introduces the risk that > bugfixes never make it back to the underlying product, because nobody > has the incentive (beyond good intentions) to land them. class="ironic">Of course, nobody would actually succumb to that > temptation. > > > See for instance the state we had before CMF 1.5.2 was released: > > http://svn.nuxeo.org/trac/pub/browser/CPSCompat/trunk/?rev=24873 > > These changes have become irrelevant now that CMF 1.5.2 is out, so the > > current code doesn't have them anymore. And I haven't forced anyone to > > release any other software just because I needed a new version of CPS > > out there. > > I learned this morning that the Plone 2.1 RC went out (I am told) with > CMF 1.5.2. The really crucial fix for them (making the pathwalk in > DirectoryView less painfully slow) only really affects people running > from SVN checkouts; OTOH, SVN is the only way to get the RC. > > > Tres. > - -- > === > Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] > Palladion Software "Excellence by Design"http://palladion.com > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.5 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFC7ivt+gerLs4ltQ4RAuqAAKDXbZV6QZV7ZNc/dBBLg2XYDmPyfgCaA8S/ > hVNeCzj+9gyOcacLkq37G7s= > =gx8q > -END PGP SIGNATURE- > ___ > Zope-CMF maillist - Zope-CMF@lists.zope.org > http://mail.zope.org/mailman/listinfo/zope-cmf > > See http://collector.zope.org/CMF for bug reports and feature requests ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CMF 1.5.3 beta?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florent Guillaume wrote: > Tres Seaver <[EMAIL PROTECTED]> wrote: > >>Because the Plone guys are trying to release a 2.1RC at OSCOM, and >>because it would be sensible for them to use the fixes made since 1.5.2 >>to the 1.5 branch, I'm wondering if we should be tagging a beta of 1.5.3. >> >>Any objections? I may or may not get around to making a release for it. > > No objection. I'll slip in a few changes to reindexObjectSecurity today > too probably. > > However I'd like to urge the "Plone guys" (95% of which don't bother to > read or post in this list) to move their collective butts and actually > implement forward-compatibility in Plone itself rather that, once more, > tying the release of a base software to their own schedule. I've been working on getting more of them focused on the maintenance of CMF: Andy McKay, Geoff Davis, and Alec Mitchell each have fixes they want to land as soon as they get cleared for SVN access. > We have been doing it in CPS for a while, in a "CPSCompat" product. It's > very easy, this is python, we can monkey-patch everything we need. The problem with that approach is that it introduces the risk that bugfixes never make it back to the underlying product, because nobody has the incentive (beyond good intentions) to land them. Of course, nobody would actually succumb to that temptation. > See for instance the state we had before CMF 1.5.2 was released: > http://svn.nuxeo.org/trac/pub/browser/CPSCompat/trunk/?rev=24873 > These changes have become irrelevant now that CMF 1.5.2 is out, so the > current code doesn't have them anymore. And I haven't forced anyone to > release any other software just because I needed a new version of CPS > out there. I learned this morning that the Plone 2.1 RC went out (I am told) with CMF 1.5.2. The really crucial fix for them (making the pathwalk in DirectoryView less painfully slow) only really affects people running from SVN checkouts; OTOH, SVN is the only way to get the RC. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC7ivt+gerLs4ltQ4RAuqAAKDXbZV6QZV7ZNc/dBBLg2XYDmPyfgCaA8S/ hVNeCzj+9gyOcacLkq37G7s= =gx8q -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CMF 1.5.3 beta?
Tres Seaver <[EMAIL PROTECTED]> wrote: > Because the Plone guys are trying to release a 2.1RC at OSCOM, and > because it would be sensible for them to use the fixes made since 1.5.2 > to the 1.5 branch, I'm wondering if we should be tagging a beta of 1.5.3. > > Any objections? I may or may not get around to making a release for it. No objection. I'll slip in a few changes to reindexObjectSecurity today too probably. However I'd like to urge the "Plone guys" (95% of which don't bother to read or post in this list) to move their collective butts and actually implement forward-compatibility in Plone itself rather that, once more, tying the release of a base software to their own schedule. We have been doing it in CPS for a while, in a "CPSCompat" product. It's very easy, this is python, we can monkey-patch everything we need. See for instance the state we had before CMF 1.5.2 was released: http://svn.nuxeo.org/trac/pub/browser/CPSCompat/trunk/?rev=24873 These changes have become irrelevant now that CMF 1.5.2 is out, so the current code doesn't have them anymore. And I haven't forced anyone to release any other software just because I needed a new version of CPS out there. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CMF 1.5.3 beta?
On 1 Aug 2005, at 06:04, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Because the Plone guys are trying to release a 2.1RC at OSCOM, and because it would be sensible for them to use the fixes made since 1.5.2 to the 1.5 branch, I'm wondering if we should be tagging a beta of 1.5.3. Any objections? I may or may not get around to making a release for it. I can handle tagging and releasing, matter of fact I *want* to do that to verify my documentation and script changes for release making from SVN and with the new naming conventions. My impression had been that 1.5.2 was the target platform for Plone 2.1, but if they need something that was fixed afterwards I can certainly throw in a quick 1.5.3 beta/release cycle. jens ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] CMF 1.5.3 beta?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Because the Plone guys are trying to release a 2.1RC at OSCOM, and because it would be sensible for them to use the fixes made since 1.5.2 to the 1.5 branch, I'm wondering if we should be tagging a beta of 1.5.3. Any objections? I may or may not get around to making a release for it. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC7a1G+gerLs4ltQ4RAjxPAJ9VJwWEFL2vNeHNLJS6vZHVmoBQCACgiIYB fF5eFj+0V76J9o5E5gylulw= =w+nJ -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
