| [e4-dev] API in e4 1.0? |
Hi, everyone.
Since this is API freeze week for 3.6 (M6), I spent a lot of time last week on those bugs that are really hard to fix because you can't break existing clients, but you want to move things forward, but the framework is so exposed via API that it's hard to do anything anymore, etc. etc.
And that got me wondering, have we said anything about the state of our API in e4 1.0?
One of the nice things about e4 is we have the freedom to iterate designs and fix "big stuff" because we aren't constrained by past mistakes. And we know we won't get things perfect in 1.0.
Obviously, the "compatibility layer" is API since it's our 3.x API. But what about the new stuff? Where do we think we are mature enough to declare API? Do we want to declare anything provisional in 1.0?
The e4 project plan has the usual disclaimers about our ability to change non-API from release to release, but I don't think we've really talked about how much API we want to release.
I've opened a bug [1] to track this discussion, and Boris suggested we talk about it on Thursday's e4 call.
susan
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=305191