As you like. I can't really make a strong case, but isn't 1.0 a consequence rather than a cause?
The cause is that API's need to still be a bit unstable and Calcite needs a release. It seems to me that if you don't want to debase the meaning of 1.0, you need to release a non-1.0 release. The logic is simple. 1.x => stable API therefore not(stable API) => not 1.0 <http://en.wikipedia.org/wiki/Contraposition> On Wed, Jan 14, 2015 at 1:51 PM, Julian Hyde <[email protected]> wrote: > You’re right, it could be a non-1.0 release. Or we could declare that the > APIs Drill wants to change are not stable. I’d prefer the latter. > > Julian > > On Jan 14, 2015, at 1:44 PM, Ted Dunning <[email protected]> wrote: > > > What can't this next release be a non-1.0 release? > > > > >
