Re: [Zope-CMF] [dev] CMF 2.1 dependencies
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think trying to come up with a list of applications that "will break" is utopian. We're not talking "locked-down walled garden" here where the vendor has control over what the customer runs. We cannot anticipate what will break, apart from very high-level (and thus not all that helpful) statements like "sorry, CMF 1.3 probably won't run on Zope 2.10". The possible software combinations out there are limitless. The list not be exhaustive or prescriptive. If all core components and "commonly used" products are not broken then making this known is helpful. Sorry, I'm just getting into the CMF otherwise I might have been able to make a more detailed suggestion. But what do you define as "core components" or "commonly used products"? Obviously all those pieces that are part of the CMF tarball will have been tested and known to work with Zope 2.10. The same is true for Plone 3.0. Keep in mind that coming up with this "commonly used software" list and then actually testing it requires time and effort. Are you volunteering? And how exactly would you test? There's tons of products out there that have no tests at all, and a lot where tests exist but don't even run out of the box. But then again unit tests may not provide a good picture, anyway, where the authors don't provide good test coverage or wrote bad tests. So now you'd have to click around to manually test all functionality. I'm also concerned that any attempt by the CMF team to identify such software would backfire in general. People would want to know why "their" software is not listed. Listing a package also implies some responsibility, and I personally refuse to guarantee that any third party product not under my control does or does not work. Certifying that it does work is the responsibility of those packages' authors, not a Zope or CMF developer/release manager job. I will always stand behind a guarantee that released stable CMF versions and their listed dependencies work together, no problem. As far as that Windows installer goes, that dicussion belongs on zope-dev or zope@zope.org, where you will get the standard answer: "Sorry, no one has stepped up to do this yet, would you like to volunteer?". I know. I was referring obliquely to the fact that Zope 2.10 probably has not been tested as much as it should have been to be considered a stable version. My personal opinion: I disagree with that statement. And not having a Zope 2.10 Windows installer would not be any obstacle to releasing CMF 2.1, at least in my view. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFSLQsRAx5nvEhZLIRAgN6AJ9AL46N58H/LbhrzfFFCQddeK8uDwCfaoki v7tGfT77xdmMFIboH9ZwJUc= =bMin -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] [dev] CMF 2.1 dependencies
Am 01.11.2006 um 14:45 schrieb Jens Vagelpohl: I think trying to come up with a list of applications that "will break" is utopian. We're not talking "locked-down walled garden" here where the vendor has control over what the customer runs. We cannot anticipate what will break, apart from very high-level (and thus not all that helpful) statements like "sorry, CMF 1.3 probably won't run on Zope 2.10". The possible software combinations out there are limitless. The list not be exhaustive or prescriptive. If all core components and "commonly used" products are not broken then making this known is helpful. Sorry, I'm just getting into the CMF otherwise I might have been able to make a more detailed suggestion. As with any Zope upgrade (or Zope-related software) upgrade, users will have to test for their specific situation. Create a test instance with the new software, copy the database across, and see what breaks. Due to the variability in peoples' setup and the software they run that is the only sane advice to give. As far as that Windows installer goes, that dicussion belongs on zope-dev or zope@zope.org, where you will get the standard answer: "Sorry, no one has stepped up to do this yet, would you like to volunteer?". I know. I was referring obliquely to the fact that Zope 2.10 probably has not been tested as much as it should have been to be considered a stable version. Charlie -- Charlie Clark Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-938-5360 GSM: +49-178-782-6226 ___ 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] [dev] CMF 2.1 dependencies
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1 Nov 2006, at 08:33, Charlie Clark wrote: Right now I believe Plone is the only customer for 2.1, but if anyone else has an objection, please speak up today. I have no problems will deprecating code and also aligning CMF with particular Zope versions. It might, however, be useful to note if any existing applications will be broken by the change. Oh, and it might be nice for someone on the Zope release team to bring out Windows versions of 2.9.5 and 2.10.0 for those who might need to try them in advance. I think trying to come up with a list of applications that "will break" is utopian. We're not talking "locked-down walled garden" here where the vendor has control over what the customer runs. We cannot anticipate what will break, apart from very high-level (and thus not all that helpful) statements like "sorry, CMF 1.3 probably won't run on Zope 2.10". The possible software combinations out there are limitless. As with any Zope upgrade (or Zope-related software) upgrade, users will have to test for their specific situation. Create a test instance with the new software, copy the database across, and see what breaks. Due to the variability in peoples' setup and the software they run that is the only sane advice to give. As far as that Windows installer goes, that dicussion belongs on zope- dev or zope@zope.org, where you will get the standard answer: "Sorry, no one has stepped up to do this yet, would you like to volunteer?". jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFSKTtRAx5nvEhZLIRAiNuAJ9OS4OsmnVaD5UrNsu70FJCbDyvhACfWwYa uk2Ju6rsLmoUs95WoN84FBA= =CVrU -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] [dev] CMF 2.1 dependencies
Am 01.11.2006 um 14:06 schrieb Jens Vagelpohl: I'd like to make Zope 2.10 required for CMF trunk (2.1). This was discussed before in this thread: http://mail.zope.org/pipermail/zope-cmf/2006-September/024813.html In my sandbox I removed the Zope 2.9 backwards compatibility code and got rid of all deprecation warnings. If there are no objections I'll check in those changes. I am personally +1 on that myself. Right now I believe Plone is the only customer for 2.1, but if anyone else has an objection, please speak up today. I have no problems will deprecating code and also aligning CMF with particular Zope versions. It might, however, be useful to note if any existing applications will be broken by the change. Oh, and it might be nice for someone on the Zope release team to bring out Windows versions of 2.9.5 and 2.10.0 for those who might need to try them in advance. Charlie -- Charlie Clark Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-938-5360 GSM: +49-178-782-6226 ___ 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] [dev] CMF 2.1 dependencies
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1 Nov 2006, at 04:27, yuppie wrote: Hi! I'd like to make Zope 2.10 required for CMF trunk (2.1). This was discussed before in this thread: http://mail.zope.org/pipermail/zope-cmf/2006-September/024813.html In my sandbox I removed the Zope 2.9 backwards compatibility code and got rid of all deprecation warnings. If there are no objections I'll check in those changes. I am personally +1 on that myself. Right now I believe Plone is the only customer for 2.1, but if anyone else has an objection, please speak up today. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFSJvXRAx5nvEhZLIRArp4AJ4p6SK1NdBh4ORTfRet2zIYDOjKRACghYmg wN1Gy2Q0Wi0F1zaa2wE0k50= =NOgw -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] [dev] CMF 2.1 dependencies
Previously yuppie wrote: > I'd like to make Zope 2.10 required for CMF trunk (2.1). This was > discussed before in this thread: > http://mail.zope.org/pipermail/zope-cmf/2006-September/024813.html +1 here. Plone 3.0 has the same Zope requirement. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ 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] [dev] CMF 2.1 dependencies
Hi! I'd like to make Zope 2.10 required for CMF trunk (2.1). This was discussed before in this thread: http://mail.zope.org/pipermail/zope-cmf/2006-September/024813.html In my sandbox I removed the Zope 2.9 backwards compatibility code and got rid of all deprecation warnings. If there are no objections I'll check in those changes. Cheers, Yuppie ___ 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
