On 9/12/06, Jim Fulton <[EMAIL PROTECTED]> wrote:
FWIW, I use the following approach:
- Early in the process, I mark every real reproducable bug as blocking.
In this last go around, this included a number of bugs that had been
around for months or years.
- Later in the process I downgrade
Hi there,
Jim Fulton wrote:
>> I know. So Martijn and I both stepped forward a small bit on this. So we
>> need some conflict resolution. :)
>
> Let Martijn do 3.3.1. Why don't you do 3.4.
Actually dividing that job up to different people, maybe on a kind of
rotation, sounds like a good plan. Wh
On Sep 12, 2006, at 1:24 PM, Christian Theune wrote:
Jim Fulton wrote:
On Sep 12, 2006, at 10:50 AM, Christian Theune wrote:
Jim Fulton wrote:
On Sep 12, 2006, at 10:33 AM, Christian Theune wrote:
- I think we want a release manager.
You're a genius! I'll just snap my fingers.
What ha
Martijn Faassen wrote at 2006-9-12 11:25 +0200:
> ...
>On the one hand core developers seem to be happy to use the trunk for
>development projects, and on the other hand we demand a lot of work
>doing bugfixes in a release, up to the point where we delay the release
>itself.
"core developers" p
Jim Fulton wrote:
> On Sep 12, 2006, at 10:50 AM, Christian Theune wrote:
>> Jim Fulton wrote:
>>> On Sep 12, 2006, at 10:33 AM, Christian Theune wrote:
>> - I think we want a release manager.
>
> You're a genius! I'll just snap my fingers.
What happened after you snapped? :
On Sep 12, 2006, at 10:50 AM, Christian Theune wrote:
Hi,
Jim Fulton wrote:
On Sep 12, 2006, at 10:33 AM, Christian Theune wrote:
- I think we want a release manager.
You're a genius! I'll just snap my fingers.
What happened after you snapped? :)
You became the release manager. Welco
On Tuesday 12 September 2006 10:13, Jim Fulton wrote:
> > Sometimes it feels to me that when Stephan or you prioritize a bug
> > that
> > you have a rough understanding of the solution,
>
> You are mistaken. Stephan should speak up on his criteria, but I
> have the impression that it is "guilt
Hey,
Jim Fulton wrote:
[snip]
I would go further. I would not unfreeze the trunk until until we've
cleaned up all open bugs, either by fixing them or rejecting them.
-1
Why, do you think we should allow old bugs to languish forever?
I think this would be a bad thing to do after every rel
Hi,
Jim Fulton wrote:
>
> On Sep 12, 2006, at 10:33 AM, Christian Theune wrote:
- I think we want a release manager.
>>>
>>> You're a genius! I'll just snap my fingers.
>>
>> What happened after you snapped? :)
>
> You became the release manager. Welcome aboard!
Can I make you my assistan
On Sep 12, 2006, at 10:33 AM, Christian Theune wrote:
- I think we want a release manager.
You're a genius! I'll just snap my fingers.
What happened after you snapped? :)
You became the release manager. Welcome aboard!
Does the application of irony indicate that we (I) should get over i
On Sep 12, 2006, at 9:53 AM, Christian Theune wrote:
Hi,
Jim Fulton wrote:
On Sep 12, 2006, at 8:58 AM, Christian Theune wrote:
...
Ack. One thing that bothers me (and it's totally possible that I'm
missing some documentation from zope.org) is that the overall
process
isn't well documente
Jim Fulton wrote:
>> Sometimes it feels to me that when Stephan or you prioritize a bug that
>> you have a rough understanding of the solution,
>
> You are mistaken. Stephan should speak up on his criteria, but I have
> the impression that it is "guilty until proven innocent". That is, I
> think
On Sep 12, 2006, at 9:50 AM, Martijn Faassen wrote:
Jim Fulton wrote:
On Sep 12, 2006, at 8:40 AM, Martijn Faassen wrote:
[snip]
One problem we have is getting things to be tested. It hardly
motivates people to test for and report bugs if their reports
don't affect he release. I think we
On Sep 12, 2006, at 9:17 AM, Christian Theune wrote:
Then your idea of perfection and mine are far apart. Letting bugs
languish for months or even years is not acceptable. Ignoreing bugs
reported during beta testing, when we get too little testing to begin
with is unacceptable.
I agree on th
On Sep 12, 2006, at 8:57 AM, Jim Fulton wrote:
I still think our quality standards for a release have been too
high. Getting people to fix more bugs is good, sure, but perhaps
we should separate this at least somewhat from the release itself.
Sorry, I agree very much. I'd be willing t
Hi,
Jim Fulton wrote:
>
> On Sep 12, 2006, at 8:58 AM, Christian Theune wrote:
> ...
>> Ack. One thing that bothers me (and it's totally possible that I'm
>> missing some documentation from zope.org) is that the overall process
>> isn't well documented, so it's hard for me (and probably other peo
Jim Fulton wrote:
On Sep 12, 2006, at 8:40 AM, Martijn Faassen wrote:
[snip]
One problem we have is getting things to be tested. It hardly
motivates people to test for and report bugs if their reports
don't affect he release. I think we have a serious problem that
needs to be addressed. I d
On Sep 12, 2006, at 8:58 AM, Christian Theune wrote:
...
Ack. One thing that bothers me (and it's totally possible that I'm
missing some documentation from zope.org) is that the overall process
isn't well documented, so it's hard for me (and probably other people)
to jump in and do stuff.
Um.
Hi,
Jim Fulton wrote:
>
> On Sep 12, 2006, at 8:40 AM, Martijn Faassen wrote:
>
>> Jim Fulton wrote:
>>> On Sep 12, 2006, at 5:25 AM, Martijn Faassen wrote:
>> [snip]
Anyway, if the Gnome project can do time-based releases *on the
date* we should be able to do it too.
>>> Maybe they ha
Morning,
Martijn Faassen wrote:
>> I don't think our problem has been perfectionism. I think our problem
>> has been a lack of will to fix things in a timely manner.
>
>> One problem we have is getting things to be tested. It hardly
>> motivates people to test for and report bugs if their repor
On Sep 12, 2006, at 8:40 AM, Martijn Faassen wrote:
Jim Fulton wrote:
On Sep 12, 2006, at 5:25 AM, Martijn Faassen wrote:
[snip]
Anyway, if the Gnome project can do time-based releases *on the
date* we should be able to do it too.
Maybe they have more volunteers.
Yes. They also have a *l
Jim Fulton wrote:
On Sep 12, 2006, at 5:25 AM, Martijn Faassen wrote:
[snip]
Anyway, if the Gnome project can do time-based releases *on the date*
we should be able to do it too.
Maybe they have more volunteers.
Yes. They also have a *lot* more to release. Their release story is also
ma
On Sep 12, 2006, at 5:25 AM, Martijn Faassen wrote:
Hi there,
Thanks for doing this work, Christian. I'm in favor of going for
Zope 3.4 on a timely basis.
Concerning the delay of Zope 3.3, I think we should consider
whether we're not too perfectionistic.
On the one hand core developers
On 9/12/06, Martijn Faassen <[EMAIL PROTECTED]> wrote:
What about a policy where we fix bugs until the release date, and then
on the release date, we actually release? Any bugs that are still in it
are going to go with it.
I totally agree. My feeling is that the x.x.0 release this time will
be
Hi there,
Thanks for doing this work, Christian. I'm in favor of going for Zope
3.4 on a timely basis.
Concerning the delay of Zope 3.3, I think we should consider whether
we're not too perfectionistic.
On the one hand core developers seem to be happy to use the trunk for
development proje
Hi,
as we're running late already on Zope 3.3 and also running into the
original alloted time for 3.4, I've taken a minute to update the RoadMap
[1].
As far as I understand the grand plan for Zope 3.4 is the eggification.
I don't see any proposal attached to that, but we better get this
rolling
26 matches
Mail list logo
