Re: [Zope3-dev] branched Zope 2.9
Andreas Jung wrote: --On 13. November 2005 11:25:21 -0500 Jim Fulton <[EMAIL PROTECTED]> wrote: ... http://www.zope.org/Collectors/Zope/collector_contents?searching=yep&Sear chableText=&status%3Alist%3Aignore_empty=Accepted&status%3Alist%3Aignore_ empty=Pending&classifications%3Alist%3Aignore_empty=bug&importances%3Alis t%3Aignore_empty=critical Ups, I got your point. I thought you were talking about 9 critical error *directly* related to Zope 2.9 e.g. the packaging issue, Five etc..I am aware of this issues. Issue marked by the issuer as critical might appear critical to them..so one needs to decide which issues are blockers. Yup. :) 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 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] branched Zope 2.9
--On 13. November 2005 11:25:21 -0500 Jim Fulton <[EMAIL PROTECTED]> wrote: ... http://www.zope.org/Collectors/Zope/collector_contents?searching=yep&Sear chableText=&status%3Alist%3Aignore_empty=Accepted&status%3Alist%3Aignore_ empty=Pending&classifications%3Alist%3Aignore_empty=bug&importances%3Alis t%3Aignore_empty=critical Ups, I got your point. I thought you were talking about 9 critical error *directly* related to Zope 2.9 e.g. the packaging issue, Five etc..I am aware of this issues. Issue marked by the issuer as critical might appear critical to them..so one needs to decide which issues are blockers. Andreas pgp9Fw9W71QVq.pgp Description: PGP signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] branched Zope 2.9
[Andreas Jung] > ... > There are no 2.9 related issues in the collector but I assume there a bunch > of unreported issues. That the Zope trunk tests fail on Windows should be a 2.9 release issue, yes? Windows test failures on Zope trunk http://www.zope.org/Collectors/Zope/1931 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] branched Zope 2.9
Andreas Jung wrote: I can only what I know of. If there are bugs then they should be documented in the collector. Of course. ... We currently have 9 critical Zope 2 bugs. Where are they documented? They should be documented in the collector or least there should be some communication on zope-dev about ongoing release issues. I can not follow every discussions on IRC (time constraints, different timezones).. ... http://www.zope.org/Collectors/Zope/collector_contents?searching=yep&SearchableText=&status%3Alist%3Aignore_empty=Accepted&status%3Alist%3Aignore_empty=Pending&classifications%3Alist%3Aignore_empty=bug&importances%3Alist%3Aignore_empty=critical 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 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] branched Zope 2.9
--On 13. November 2005 10:55:19 -0500 Jim Fulton <[EMAIL PROTECTED]> wrote: Do you also track bugs? I can only what I know of. If there are bugs then they should be documented in the collector. I'm not sure how, aside from feature completeness, we decide we're ready for a beta. For Zope 3, we prioritize bugs as critical to indicate that they must be resolved before a release. Is there a similar process for Zope 2. There are no 2.9 related issues in the collector but I assume there a bunch of unreported issues. I realize that you make a significant contribution just making the release. Jup. I'm not sure if you are also trying to be the one to decide (or to manage the decision) to make releases. The decision to make release basically depends on the OK from everyone having contributed lately to the trunk. This affects basically the Five contributions, the zpkg changes and some changes from you. So that's why was asking about the status (see my other posting on zope-dev). We currently have 9 critical Zope 2 bugs. Where are they documented? They should be documented in the collector or least there should be some communication on zope-dev about ongoing release issues. I can not follow every discussions on IRC (time constraints, different timezones).. Andreas pgpV2rQD1q6lz.pgp Description: PGP signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] branched Zope 2.9
Andreas Jung wrote: --On 12. November 2005 22:08:38 -0500 Chris McDonough <[EMAIL PROTECTED]> wrote: FYI (this is mostly for the benefit of the Five folks), I've created a Zope 2.9 branch from the trunk as of about 10 minutes ago. This branch is frozen for feature work; it may need some changing of externals to reflect what we want the initial version of Zope 3 that we want 2.9 to ship with. I don't know what that version is, so this is a note to say that if these externals changes get made on the Zope 2 trunk, please also make them on the 2.9 branch. I would have created the 2.9 branch in case the current trunk would be ready to branch. At least one week ago there were unresolved issues (with zpkg I think) that deferred the 2.9 release (scheduled for last Monday). So in general what is the current state of the remaining work to get 2.9b1 out to the people? Do you also track bugs? I'm not sure how, aside from feature completeness, we decide we're ready for a beta. For Zope 3, we prioritize bugs as critical to indicate that they must be resolved before a release. Is there a similar process for Zope 2. I realize that you make a significant contribution just making the release. I'm not sure if you are also trying to be the one to decide (or to manage the decision) to make releases. We currently have 9 critical Zope 2 bugs. I don't know if that has the same significane as for Zope 3. 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 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] branched Zope 2.9
--On 12. November 2005 22:08:38 -0500 Chris McDonough <[EMAIL PROTECTED]> wrote: FYI (this is mostly for the benefit of the Five folks), I've created a Zope 2.9 branch from the trunk as of about 10 minutes ago. This branch is frozen for feature work; it may need some changing of externals to reflect what we want the initial version of Zope 3 that we want 2.9 to ship with. I don't know what that version is, so this is a note to say that if these externals changes get made on the Zope 2 trunk, please also make them on the 2.9 branch. I would have created the 2.9 branch in case the current trunk would be ready to branch. At least one week ago there were unresolved issues (with zpkg I think) that deferred the 2.9 release (scheduled for last Monday). So in general what is the current state of the remaining work to get 2.9b1 out to the people? Andreas pgpdCmBJ7gtTt.pgp Description: PGP signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] branched Zope 2.9
FYI (this is mostly for the benefit of the Five folks), I've created a Zope 2.9 branch from the trunk as of about 10 minutes ago. This branch is frozen for feature work; it may need some changing of externals to reflect what we want the initial version of Zope 3 that we want 2.9 to ship with. I don't know what that version is, so this is a note to say that if these externals changes get made on the Zope 2 trunk, please also make them on the 2.9 branch. - C ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com