On Sat, May 17, 2014 at 4:52 PM, Mark Hamstra <m...@clearstorydata.com> wrote: > Which of the unresolved bugs in spark-core do you think will require an > API-breaking change to fix? If there are none of those, then we are still > essentially on track for a 1.0.0 release.
I don't have a particular one in mind, but look at https://issues.apache.org/jira/browse/SPARK-1817?filter=12327229 for example. There are 10 issues marked blocker or critical, that are targeted at Core / 1.0.0 (or unset). Many are probably not critical, not for 1.0, or wouldn't require a big change to fix. But has this been reviewed then -- can you tell? I'd be happy for someone to tell me to stop worrying, yeah, there's nothing too big here. > The number of contributions and pace of change now is quite high, but I > don't think that waiting for the pace to slow before releasing 1.0 is > viable. If Spark's short history is any guide to its near future, the pace > will not slow by any significant amount for any noteworthy length of time, I think we'd agree core is the most important part. I'd humbly suggest fixes and improvements to core remain exceptionally important after 1.0 and there is a long line of proposed changes, most good. Would be great to really burn that down. Maybe that is the kind of thing I personally would have preferred to see before a 1.0, but it's not up to me and there are other factors at work here. I don't object strongly or anything.
