[Zope3-dev] Re: branched Zope 2.9
Florent Guillaume wrote: > BTW I'm for removing the 2.9 branch for now. You didn't, so I presume 2.9 branch stays? It's important to clear the status of this branch because bugfixes need to be merged to it (see my email about Tres' bugfix, for example). By the way, in the future, just to avoid confusion, I think release branches should be made by the release manager (in thise case Andreas Jung). They clearly fall under their responsibility and supervision. I still think it was a good thing to create the branch now because I agree with Tres' general argument that a feature freeze on the trunk hinders on-going development. The trunk should never be in any freeze state. That's what release branches are for. Thus, the Zope 2.9 and 3.2 branches should have been made November 1st. Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: branched Zope 2.9
Tim Peters wrote: > [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 I just followed up on http://www.zope.org/Collectors/Zope/1947. The Five test failure is a known issue and only occurs when running the test among others. Running it by itself works. Don't ask me why, if I'd know I'd already have fixed it... ;) Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: branched Zope 2.9
--On 14. November 2005 02:42:31 +0100 Florent Guillaume <[EMAIL PROTECTED]> wrote: [Reply-To and Followup-To zope-dev] Andreas Jung wrote: Anyway if we want to go further we need to schedule bug days. One per week, or something like that. Otherwise nobody will set aside the time to discuss, investigate and fix the current bugs. Right, right, but there must be enough people to fix bugs...the last bugs days we had were not sooo successful. Then let's try again :) You're going to organize them? :-) -aj pgpSDOb3FCt8m.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] Re: branched Zope 2.9
[Reply-To and Followup-To zope-dev] Andreas Jung wrote: Anyway if we want to go further we need to schedule bug days. One per week, or something like that. Otherwise nobody will set aside the time to discuss, investigate and fix the current bugs. Right, right, but there must be enough people to fix bugs...the last bugs days we had were not sooo successful. Then let's try again :) There is no way to enforce contributors to fix bugs. Speaking for myself I look at bugs from time to time and see what I can fix. There are bunch of bugs where you don't know if it is a bug or a feature...it's basically a question of having time... But having specific days set aside is still a good incentive. Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: branched Zope 2.9
--On 13. November 2005 20:33:01 +0100 Florent Guillaume <[EMAIL PROTECTED]> wrote: Anyway if we want to go further we need to schedule bug days. One per week, or something like that. Otherwise nobody will set aside the time to discuss, investigate and fix the current bugs. Right, right, but there must be enough people to fix bugs...the last bugs days we had were not sooo successful. There is no way to enforce contributors to fix bugs. Speaking for myself I look at bugs from time to time and see what I can fix. There are bunch of bugs where you don't know if it is a bug or a feature...it's basically a question of having time... -aj pgpSbJILq4iLv.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] Re: branched Zope 2.9
Andreas Jung 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. Anyway if we want to go further we need to schedule bug days. One per week, or something like that. Otherwise nobody will set aside the time to discuss, investigate and fix the current bugs. BTW I'm for removing the 2.9 branch for now. Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: 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? There are a couple of things that need to be addressed: - Make zpkg support top-level modules. I've started work on this but I had to do some other stuff in the mean time (was busy with my actual work). I'll try to look at it this week. - Revise the zope.app stitching and also decide what of Zope 3 goes into Zope 2.8 and what not. I guess people want zope.formlib, for example, and it would make sense to include it in Zope 2.9 if it's also in Zope 3.2. - Sort out any remaining issues with the in-place build system. IIRC, only two things aren't working anymore: The ability to build out-of-place (e.g. create a build tree in an empty dir) and the ability to do "make install" from a checkout. The zpkg in-place build system doesn't support those, somebody would have to make it support it if they wanted these features. Maybe there's more, I'm not claiming to be complete on this. Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
