[Swift-devel] Re: Coaster capabilities for release 0.9

[Mihael Hategan]

On Tue, 2009-04-21 at 10:57 -0500, Michael Wilde wrote:
> was: Re: [Swift-devel] coaster block allocations
> 
> I have not been able to try this yet - been working on grant deadlines.
> 
> But regarding an "idea of how things (will) work" - please send an 
> update on the coaster development - are you proceeding with the 3-level 
> allocation strategy you outlined in a prior thread, and how is that 
> progressing?

There's a working algorithm which I'm now working to get into the
coasters.

> 
> What is on the list of priority fixes or enhancements to coasters?

I'm focusing on the above.

> 
> Which of these can make it into 0.9? (I would like see 0.9 have a highly 
> usable coaster release with a converging set of capabilities. I would 
> argue to delay 0.9 by up to 2 weeks to get it in, if needed enhancements 
> are close)

I'd argue against it, because it's a major change and it would need more
testing than that.

> 
> I agree with Ben that coaster testing (and implicitly coaster stability) 
>   is important for this release; I would like to see us push to get the 
> feature into a state where its broadly usable and heavily used.

Yes. All the things we do we want to get into a state where it's broadly
usable and heavily used.