[Squeakfoundation]KCP & 3.6

Stephane Ducasse ducasse at iam.unibe.ch
Fri Jun 20 13:40:15 CEST 2003


Hi daniel

I do not ask to wait that KCP is finshed because it may last at least 
more than 6 months
and is a background effort.
Still all the changes until KCP-0089 could easily gets in because else 
they will rot.

So we are few to do that so our code should not rot else we will stop.

Stef


On Friday, June 20, 2003, at 08:50 AM, Daniel Vainsencher wrote:

> I disagree with the current calls to delay the release. If we wait for
> everyone to get whatever matters to them in, we might never make a
> release again :-) I don't see anything wrong with stuff waiting for 3.7
> - DecPools included.
>
> I know a few of us feel "in the middle of" various projects, but I 
> think
> the release process has value too - it reminds us to clean the table
> every so often. I think between the KCP deprecations and the network
> rewrite, we've had enough change that it will do us good to focus on
> stability before we keep moving ahead.
>
> More generally - if we think about the process as a whole, not just the
> particular point in time were in, the only right kinds of reasons to
> delay the move to beta are "it doesn't meet our functionality goals". A
> more specific example is "without this new function, all of this other
> stuff we inserted makes no sense AND it is hard to remove that stuff".
> Only right kind of reason to avoid moving from beta to gamma is "this
> version doesn't meet our stability goals". Which I think should be 
> "this
> version should be stabler than the previous one".
>
> So a one week delay of beta to insert parts of KCP that relate to 
> what's
> already in makes a little sense. Delaying by a month just to get more
> stuff in now that the harvesting process is livelier, seems unjustified
> to me - we can get that after the version fork.
>
> Speaking of which - at which stage do we create the 3.7 update stream?
> last time we did it on entry to beta, IIRC, yet some might say entry to
> gamma is more reasonable. What do we think?
>
> Daniel
>
>
> Tim Rowledge <tim at sumeru.stanford.edu> wrote:
>> I don't think we're anywhere near ready for beta right now; just for 
>> an
>> example in my area there is the DeclarativePools stuff to decide on.
>>
>> tim
>> --
>> Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
>> Strange OpCodes: KFP: Kindle Fire in Printer
>> _______________________________________________
>> Squeakfoundation mailing list
>> Squeakfoundation at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/listinfo/squeakfoundation
> _______________________________________________
> Squeakfoundation mailing list
> Squeakfoundation at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/squeakfoundation
>



More information about the Squeakfoundation mailing list