[Swift-devel] Planning next set of Swift features and releases

[Ben Clifford]

On Tue, 21 Apr 2009, Michael Wilde wrote:

> Before 0.9 is released, I want to discuss an agreed upon sequence for the next
> set of enhancements and improvements, and a target set of dates and release
> numbers for them.

I think the below is good to discuss. I don't see how it affects the 
transition (or not) of 0.9rc2 to 0.9.

> It is a minor issue, but I see Swift 1.0 as having some greater 
> significance as a release number.

Yes, it does have significance. Though until you mentioned it today, I 
hadn't regard Swift as being

> Also minor but going from 0.9 to 0.10 is odd.

Not really. Lots of software uses . as a field separate for integers, 
rather than as a decimal-fraction indicator.

> The significance of calling something 1.0 thought will extend to funding 
> issues, as our next NSF report will be due soon - June 1 I think - and 
> concurrently I need to go to NSF and other agencies for continued 
> funding, probably with an unsolicited proposal.

OK. I don't really care what the versions are called as long as they are 
clearly ordered so if you have a preference for 0.9 + 2 to be 1.0 thats 
fine. Or 0.9 + 1 be 1.0.

> My preference is to do 2 or more point releases in the next 16 weeks and 
> shoot for 1.0 by the end of August.

2 releases matches the existing release schedule for that time period, 
assuming that the first release candidate is released for each. Rough 
dates on that schedule are late June and late August (so 1.0 would be the 
august one)

However, rushing to put less-well tested code into trunk is likely to 
break the first-rc-is-release goal, as well as lowering the quality of 
experience for people who build from SVN.

====

> Condor-G support

That exists in 0.9rc2, at least for regular job submission.

>  - why iterate seems hard to use

Post some stuff to swift-devel about htat.

--