On Thursday, April 8, 2004, at 06:31 AM, Nathanael Schärli wrote:

>> As to whether this "fix" should go in 3.7beta or wait until 3.8alpha,
>> that's hard to say.  Possibly it could go in 3.7beta if we
>> made it close
>> browser windows, etc.  It seems like a big enough change that
>> we might
>> want to wait until 3.8alpha though, if it's not too urgent.
>> On the plus
>> side, Dan has been talking about an accelerated schedule for 3.8
>> (June/July for 3.8final), so if it were to wait for 3.8, you wouldn't
>> have to wait *too* long.
>
> I'm torn as well. On one hand, it would be good to have it in 3.7beta
> because it fixes some bugs in the SystemChangeNotification framework 
> and
> with the drag'n'drop. However, these are all minor things and most
> programmers will never run into them.
>
> Also, this changeset is quite big and so there is definitely a 
> potential
> that it breaks some other things. (Well, I have tested it quite
> extensively, but I can't give a guarantee). Therefore, I can totally
> understand that it is too big of a risk to introduce it so late in the
> beta cycle.

I think we should wait for 3.8alpha then.

> For me, the most important thing is that this changeset gets
> incoprorated before the code gets "out of date" (i.e., there is new 
> code
> modifying the same methods that are part of this changeset). But since
> this changeset mainly affects kernel methods, it should be fine if we
> wait until 3.8alpha.

Right, I don't think there will be a problem with it getting "out of 
date".  If we approve this and also mark it "for 3.8alpha", I can plan 
on incorporating it right at the beginning of 3.8alpha.  The only other 
big change planned for the very beginning of 3.8alpha is the i18n 
stuff, but even though that's a big change, I think there will probably 
be no overlap with your changes.

- Doug