[Swift-devel] Coaster capabilities for release 0.9

[Michael Wilde]

 > Which should I rather do now, continue implementing block allocations,
 > or sort out discussions about coasters from the mailing list?

You should do this:

First send a sentence or two on how block allocations are going: whats 
involved, and how long you think they will take till checked in. What 
kind of testing will be required to ensure functional and stable.

Then continue developing them.

Between now and Friday, do the list I asked for.

 > (i.e. would you please let me do my job?)

Yes.

I know development takes concentration. To achieve that, you manage your 
time, and the rate at which you read and answer email or take any other 
interrupts.

If something needs immediate attention, I or others say so, or your best 
judgment does. If not, it doesn't, but needs eventual attention.

A list of coaster issues was started on swift-devel Feb 13:
http://mail.ci.uchicago.edu/pipermail/swift-devel/2009-February/004511.html

A report on progress and summary of open design issues and work 
remaining would benefit everyone.

Find a good stopping point in the next few days, then make list of work 
items and design and testing issues on coasters.

Then discuss and get feedback. Then develop what you listed. Then 
repeat. That *is* your job.