Re: [Zope-dev] Re: Reminder: feature freeze November 1.
On Mon, 2005-11-14 at 10:22 -0500, Tim Peters wrote: ... > Turns out the Five tests that were failing on Windows also fail on > Linux, but the failing tests don't run unless you pass ``--all`` to > test.py (which I normally do, but I guess most people don't, in which > case "most people" wouldn't see these failures). I opened a new issue > about that: > > http://www.zope.org/Collectors/Zope/1947 Ah. I'll add --all to the buildbot configs. JIm ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Reminder: feature freeze November 1.
[Tres Seaver] > test.py in the root is the likely culprit, as it is mucking with > sys.path. Does this patch make the Windows tests pass? > > - --- test.py (revision 40087) > +++ test.py (working copy) > @@ -30,7 +30,7 @@ > if shome: > shome = os.path.abspath(shome) > else: > - -shome = os.path.join(zhome, 'lib/python') > +shome = os.path.join(zhome, 'lib', 'python') > elif shome: > shome = os.path.abspath(shome) > zhome = os.path.dirname(os.path.dirname(shome)) Well spotted! It (plus the later patch) does fix the checkDuplicate test failure on Windows, and I closed issue 1931. Turns out the Five tests that were failing on Windows also fail on Linux, but the failing tests don't run unless you pass ``--all`` to test.py (which I normally do, but I guess most people don't, in which case "most people" wouldn't see these failures). I opened a new issue about that: http://www.zope.org/Collectors/Zope/1947 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Reminder: feature freeze November 1.
Dang, that's embarassing. Thanks Tres! On Sun, 2005-11-13 at 23:43 -0500, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Mark Hammond wrote: > >>>Not on Windows: > >>> > >>>Windows test failures on Zope trunk > >>>http://www.zope.org/Collectors/Zope/1931 > >>> > >>> > >>> > CMF-trunk runs fine on the Zope trunk, etc. > >>> > >>> > >>>Certainly agree it would help to have a specific list of what (if > >>>anything) still needs to fixed. FWIW, I don't expect Windows test > >>>failures to hold up a beta release (note that I didn't say that's a > >>>policy I agree with ;-)). > >> > >>Without Windows-centric developers who are motivated to investigate and > >>fix those bugs, I don't know what else we can do. > > > > > > That bugs points at > > http://mail.zope.org/pipermail/zope-dev/2005-October/025512.html, which > > quotes Tim as saying: > > > > : No idea where this slash-vs-backslash confusion ultimately comes from, > > : though. Who recently checked code in hard-coding "/" as a path > > : separator? > > > > So in this specific example, the problem seems less a lack of Windows > > centric developers, but more an abundance of non-Windows-centric developers > > :) > > > > These test failures appear at first glance to not be windows specific at > > all - just possibly pointing at non-portable code written by others. As a > > Windows developer, I'm afraid I have no idea where I would start looking for > > this bug. > > > test.py in the root is the likely culprit, as it is mucking with > sys.path. Does this patch make the Windows tests pass? > > - --- test.py (revision 40087) > +++ test.py (working copy) > @@ -30,7 +30,7 @@ > if shome: > shome = os.path.abspath(shome) > else: > - -shome = os.path.join(zhome, 'lib/python') > +shome = os.path.join(zhome, 'lib', 'python') > elif shome: > shome = os.path.abspath(shome) > zhome = os.path.dirname(os.path.dirname(shome)) > > > > Tres. > - -- > === > Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] > Palladion Software "Excellence by Design"http://palladion.com > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.1 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFDeBX3+gerLs4ltQ4RAiMdAKC7L8kACTUcTON76ch5bLNEkzO60gCgmAWw > tEeI08XK7m7PP3wD3Kwt9xE= > =0aEf > -END PGP SIGNATURE- > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Reminder: feature freeze November 1.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: > Mark Hammond wrote: > >Not on Windows: > > Windows test failures on Zope trunk > http://www.zope.org/Collectors/Zope/1931 > > > > >>CMF-trunk runs fine on the Zope trunk, etc. > > >Certainly agree it would help to have a specific list of what (if >anything) still needs to fixed. FWIW, I don't expect Windows test >failures to hold up a beta release (note that I didn't say that's a >policy I agree with ;-)). Without Windows-centric developers who are motivated to investigate and fix those bugs, I don't know what else we can do. >>> >>> >>>That bugs points at >>>http://mail.zope.org/pipermail/zope-dev/2005-October/025512.html, which >>>quotes Tim as saying: >>> >>>: No idea where this slash-vs-backslash confusion ultimately comes from, >>>: though. Who recently checked code in hard-coding "/" as a path >>>: separator? >>> >>>So in this specific example, the problem seems less a lack of Windows >>>centric developers, but more an abundance of non-Windows-centric developers >>>:) >>> >>>These test failures appear at first glance to not be windows specific at >>>all - just possibly pointing at non-portable code written by others. As a >>>Windows developer, I'm afraid I have no idea where I would start looking for >>>this bug. > > > > test.py in the root is the likely culprit, as it is mucking with > sys.path. Does this patch make the Windows tests pass? > > --- test.py (revision 40087) > +++ test.py (working copy) > @@ -30,7 +30,7 @@ > if shome: > shome = os.path.abspath(shome) > else: > -shome = os.path.join(zhome, 'lib/python') > +shome = os.path.join(zhome, 'lib', 'python') > elif shome: > shome = os.path.abspath(shome) > zhome = os.path.dirname(os.path.dirname(shome)) > > Whoops, needs another one, too: - --- test.py (revision 40091) +++ test.py (working copy) @@ -42,7 +42,7 @@ else: # No zope home, assume that it is the script directory zhome = os.path.abspath(os.path.dirname(sys.argv[0])) - -shome = os.path.join(zhome, 'lib/python') +shome = os.path.join(zhome, 'lib', 'python') sys.path.insert(0, shome) Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDeBkn+gerLs4ltQ4RAuyiAKCI5i2L4PvNnuw6lRq873VpBgw1YACdHPlO V6YGX2AQcAvoHcyHSnTbWgI= =BfFn -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Reminder: feature freeze November 1.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Hammond wrote: >>>Not on Windows: >>> >>>Windows test failures on Zope trunk >>>http://www.zope.org/Collectors/Zope/1931 >>> >>> >>> CMF-trunk runs fine on the Zope trunk, etc. >>> >>> >>>Certainly agree it would help to have a specific list of what (if >>>anything) still needs to fixed. FWIW, I don't expect Windows test >>>failures to hold up a beta release (note that I didn't say that's a >>>policy I agree with ;-)). >> >>Without Windows-centric developers who are motivated to investigate and >>fix those bugs, I don't know what else we can do. > > > That bugs points at > http://mail.zope.org/pipermail/zope-dev/2005-October/025512.html, which > quotes Tim as saying: > > : No idea where this slash-vs-backslash confusion ultimately comes from, > : though. Who recently checked code in hard-coding "/" as a path > : separator? > > So in this specific example, the problem seems less a lack of Windows > centric developers, but more an abundance of non-Windows-centric developers > :) > > These test failures appear at first glance to not be windows specific at > all - just possibly pointing at non-portable code written by others. As a > Windows developer, I'm afraid I have no idea where I would start looking for > this bug. test.py in the root is the likely culprit, as it is mucking with sys.path. Does this patch make the Windows tests pass? - --- test.py (revision 40087) +++ test.py (working copy) @@ -30,7 +30,7 @@ if shome: shome = os.path.abspath(shome) else: - -shome = os.path.join(zhome, 'lib/python') +shome = os.path.join(zhome, 'lib', 'python') elif shome: shome = os.path.abspath(shome) zhome = os.path.dirname(os.path.dirname(shome)) Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDeBX3+gerLs4ltQ4RAiMdAKC7L8kACTUcTON76ch5bLNEkzO60gCgmAWw tEeI08XK7m7PP3wD3Kwt9xE= =0aEf -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Reminder: feature freeze November 1.
--On 13. November 2005 19:05:44 -0500 Tres Seaver <[EMAIL PROTECTED]> wrote: Which bugs? Sombebody needs to define this, or else risk having the "outsiders" just walk away. *I* know of no showstoppers: all unit tests are passing, CMF-trunk runs fine on the Zope trunk, etc. About one week ago I tried to build a test release using the HEAD. At that time there were open issues concerning zpgk (as Philikon also wrote in another posting). E.g. making the source tarball did not work properly. So being unable to build a source tarball is definitely a blocker for me. Andreas pgpTkc6LTylC5.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Reminder: feature freeze November 1.
[Tim] >>> Windows test failures on Zope trunk >>> http://www.zope.org/Collectors/Zope/1931 [Tres] >> Without Windows-centric developers who are motivated to investigate and >> fix those bugs, I don't know what else we can do. [Mark Hammond] > That bugs points at > http://mail.zope.org/pipermail/zope-dev/2005-October/025512.html, which > quotes Tim as saying: > > : No idea where this slash-vs-backslash confusion ultimately comes from, > : though. Who recently checked code in hard-coding "/" as a path > : separator? > > So in this specific example, the problem seems less a lack of Windows > centric developers, but more an abundance of non-Windows-centric developers > :) > > These test failures appear at first glance to not be windows specific at > all - just possibly pointing at non-portable code written by others. As a > Windows developer, I'm afraid I have no idea where I would start looking for > this bug. Alas, I was directed not to work on this bug report "on the clock", and I haven't had spare time to donate to it (of course there's the usually irony with that: by now I've probably spent 3x as long typing about these bugs as it would have taken to fix them :-( ...). Because I'm sure I noticed the bug within a day or two of its first appearance, the obvious approach is to revert back to earlier revisions of the trunk until finding the checkin that caused it. I thought I wrote up enough clues on zope-dev at the time that whoever checked in the responsible change would think "ah, that's related to what I did!" at once. Alas again, nobody noticed. So that's a clear path to fixing this one: pinning the blame should be sufficient ;-) In the absence of the guilty party noticing they were to blame, it takes someone on Windows to do the binary search required (because someone on Linux won't see the failure). BTW, notice that the Python tracebacks had exactly the same \ vs / mixup in the same place (between "lib" and "python") as the two originally failing tests. That suggests (but doesn't prove) that a change to sys.path is the ultimate cause. BTW2, I have no idea why the later-failing Five test started failing on Windows, and didn't spend any time investigating that one. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Re: Reminder: feature freeze November 1.
> > Not on Windows: > > > > Windows test failures on Zope trunk > > http://www.zope.org/Collectors/Zope/1931 > > > > > >>CMF-trunk runs fine on the Zope trunk, etc. > > > > > > Certainly agree it would help to have a specific list of what (if > > anything) still needs to fixed. FWIW, I don't expect Windows test > > failures to hold up a beta release (note that I didn't say that's a > > policy I agree with ;-)). > > Without Windows-centric developers who are motivated to investigate and > fix those bugs, I don't know what else we can do. That bugs points at http://mail.zope.org/pipermail/zope-dev/2005-October/025512.html, which quotes Tim as saying: : No idea where this slash-vs-backslash confusion ultimately comes from, : though. Who recently checked code in hard-coding "/" as a path : separator? So in this specific example, the problem seems less a lack of Windows centric developers, but more an abundance of non-Windows-centric developers :) These test failures appear at first glance to not be windows specific at all - just possibly pointing at non-portable code written by others. As a Windows developer, I'm afraid I have no idea where I would start looking for this bug. Mark ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Reminder: feature freeze November 1.
FWIW, a patched setup.py that appears to compile all known Z2 and Z3 extensions successfully (at least it completes and Zope starts) which doesn't use any zpkg extensions is available at http://www.plope.com/static/misc/setup.py . I took this from the old "setup.py" before Phil checked in his zpkg fixes, and added an Extension directive for the i18nmessageid C extension. It also requires a change to two files in Zope 3: Index: security/_proxy.c === --- security/_proxy.c (revision 40034) +++ security/_proxy.c (working copy) @@ -17,7 +17,7 @@ */ #include -#include "zope.proxy/proxy.h" +#include "zope/proxy/proxy.h" static PyObject *__class__str = 0, *__name__str = 0, *__module__str = 0; and Index: app/container/_zope_proxy_proxy.c === --- app/container/_zope_proxy_proxy.c (revision 40034) +++ app/container/_zope_proxy_proxy.c (working copy) @@ -28,7 +28,7 @@ #include "modsupport.h" #define PROXY_MODULE -#include "zope.proxy/proxy.h" +#include "zope/proxy/proxy.h" static PyTypeObject ProxyType; - C On Sun, 2005-11-13 at 19:36 -0500, Jim Fulton wrote: > On Sun, 2005-11-13 at 19:20 -0500, Tres Seaver wrote: > ... > > Note that of all the recent changes, I would jettison zpkg-based builds > > *first* if our timebox is at risk; I certainly wouldn't agree with > > leaving the trunk frozen due to issues with a *very* recently-proposed > > change which provides no measureable benefit to the users (as opposed to > > maintainers). > > Fair enough, but without zpkg there will be a lot more stitching work to > do. Way too much of zope.app is stitched in at this point. That's not > a problem if we use zpkg to make the distribution. > > Jim > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Reminder: feature freeze November 1.
On Sun, 2005-11-13 at 19:20 -0500, Tres Seaver wrote: ... > Note that of all the recent changes, I would jettison zpkg-based builds > *first* if our timebox is at risk; I certainly wouldn't agree with > leaving the trunk frozen due to issues with a *very* recently-proposed > change which provides no measureable benefit to the users (as opposed to > maintainers). Fair enough, but without zpkg there will be a lot more stitching work to do. Way too much of zope.app is stitched in at this point. That's not a problem if we use zpkg to make the distribution. Jim ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Reminder: feature freeze November 1.
On Sun, 2005-11-13 at 19:05 -0500, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Jim Fulton wrote: > > Paul Winkler wrote: > > > >> On Tue, Oct 18, 2005 at 07:21:08AM -0400, Jim Fulton wrote: > >> > >>> This is a reminder that there will be a feature freeze for the December > >>> Zope releases on November 1. > >> > >> > >> > >> OK. I thought there was going to be a 2.9 branch by now, > >> but I don't see one. Is the trunk totally frozen now or what? > > > > > > Yes, no new features. > > > >> Is it too late to land my long-forgotten configure changes > >> as discussed at > >> http://mail.zope.org/pipermail/zope/2004-July/151839.html ? > > > > > > Yes > > > > The sooner we're ready for the first beta, the sooner we can > > make the beta and the branch. We need more volunteers to help > > with fixing bugs. > > Which bugs? Sombebody needs to define this, or else risk having the > "outsiders" just walk away. I'm not sure what you mean by outsiders. You're right, someone needs to define this. For Zope 3, the release manager goes through the collector and marks bugs that have to be fixed before the release as critical. I really don't know what the process is for Zope 2, but I did not that there were 9 bugs in the collector marked critical. In any case, the release manager should make the call. Jim ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Reminder: feature freeze November 1.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Peters wrote: > [Tres Seaver] > ... > >>Which bugs? Sombebody needs to define this, or else risk having the >>"outsiders" just walk away. > > > Insiders too ;-) > > >>*I* know of no showstoppers: all unit tests are passing, > > > Not on Windows: > > Windows test failures on Zope trunk > http://www.zope.org/Collectors/Zope/1931 > > >>CMF-trunk runs fine on the Zope trunk, etc. > > > Certainly agree it would help to have a specific list of what (if > anything) still needs to fixed. FWIW, I don't expect Windows test > failures to hold up a beta release (note that I didn't say that's a > policy I agree with ;-)). Without Windows-centric developers who are motivated to investigate and fix those bugs, I don't know what else we can do. Note that of all the recent changes, I would jettison zpkg-based builds *first* if our timebox is at risk; I certainly wouldn't agree with leaving the trunk frozen due to issues with a *very* recently-proposed change which provides no measureable benefit to the users (as opposed to maintainers). Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDd9hZ+gerLs4ltQ4RArdzAKDYpo0rFsX6ZOcDbwDBlN0THVm1HgCfVgN4 LY3dLr1YAW8Ycvu7EXiiH5M= =pjmb -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Reminder: feature freeze November 1.
[Tres Seaver] ... > Which bugs? Sombebody needs to define this, or else risk having the > "outsiders" just walk away. Insiders too ;-) > *I* know of no showstoppers: all unit tests are passing, Not on Windows: Windows test failures on Zope trunk http://www.zope.org/Collectors/Zope/1931 > CMF-trunk runs fine on the Zope trunk, etc. Certainly agree it would help to have a specific list of what (if anything) still needs to fixed. FWIW, I don't expect Windows test failures to hold up a beta release (note that I didn't say that's a policy I agree with ;-)). ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Reminder: feature freeze November 1.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Fulton wrote: > Paul Winkler wrote: > >> On Tue, Oct 18, 2005 at 07:21:08AM -0400, Jim Fulton wrote: >> >>> This is a reminder that there will be a feature freeze for the December >>> Zope releases on November 1. >> >> >> >> OK. I thought there was going to be a 2.9 branch by now, >> but I don't see one. Is the trunk totally frozen now or what? > > > Yes, no new features. > >> Is it too late to land my long-forgotten configure changes >> as discussed at >> http://mail.zope.org/pipermail/zope/2004-July/151839.html ? > > > Yes > > The sooner we're ready for the first beta, the sooner we can > make the beta and the branch. We need more volunteers to help > with fixing bugs. Which bugs? Sombebody needs to define this, or else risk having the "outsiders" just walk away. *I* know of no showstoppers: all unit tests are passing, CMF-trunk runs fine on the Zope trunk, etc. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDd9TX+gerLs4ltQ4RAjXcAKDFrEscRwaX2k/o5ggzFnRg8ZzjtgCgmwLO 4rd4lBBcwUKTalOOjJ7k+HA= =xcdb -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Reminder: feature freeze November 1.
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Fulton wrote: This is a reminder that there will be a feature freeze for the December Zope releases on November 1. No new features for the November releases should be added after October 31. The Zope trunks should be stable and ready for a beta release on November 1. We are committed to time-based releases. This means we need to be very disciplined about deadlines. If a cool new feature isn't quite ready before November 1, then it could be be included in the June release, for which the feature freeze will be May 1. Cool. I like the way the Ubuntu guys describe their freeze / process: http://lists.ubuntu.com/archives/ubuntu-devel/2005-February/004077.html I don't know what would qualify for "release goals" versus "targets of opportunity" for this cycle, though. Me neither. I have a sense that they are being a lot more formal about their process than we are though. Perhaps we should be more formal, but I kind of doubt it. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Reminder: feature freeze November 1.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Fulton wrote: > > This is a reminder that there will be a feature freeze for the December > Zope releases on November 1. No new features for the November releases > should > be added after October 31. The Zope trunks should be stable and ready > for a beta > release on November 1. > > We are committed to time-based releases. This means we need to be very > disciplined about deadlines. If a cool new feature isn't quite > ready before November 1, then it could be be included in the June > release, for which the feature freeze will be May 1. Cool. I like the way the Ubuntu guys describe their freeze / process: http://lists.ubuntu.com/archives/ubuntu-devel/2005-February/004077.html I don't know what would qualify for "release goals" versus "targets of opportunity" for this cycle, though. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDVN/m+gerLs4ltQ4RAnc2AJ9zcULEgze+3to3Iqmy5xU2QAisfwCfSzy3 4r40IYdK4ytScTAXObp3cgk= =hzGm -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
