Thank you, Panos and Owen. Then, I'll make a PR to update the Apache ORC website to make it official.
Bests, Dongjoon. On Wed, Apr 28, 2021 at 2:49 PM Owen O'Malley <[email protected]> wrote: > The goal was to follow semantic versioning. Clearly the 1.6 release broke > too much of the interface and made clear how much of the implementation > Hive and LLAP are accessing. Certainly as the two projects with the deepest > integration, we should build Hive and Spark with the ORC 1.7 rcs before > they are released. > > .. Owen > > On Wed, Apr 14, 2021 at 10:10 AM Panos Garefalakis <[email protected]> > wrote: > > > Hey Dongjoon, > > > > +1 on this, with 1.7 close to release we should have a way to move > > forward without breaking compatibility. > > Wondering if it would make sense to annotate our code on publicly facing > > methods to make this easier to enforce. > > > > Cheers, > > Panagiotis > > > > On Thu, Apr 8, 2021 at 6:36 PM Dongjoon Hyun <[email protected]> > wrote: > > > > > Hi, All. > > > > > > We know that there were some struggles to migrate from Apache ORC 1.5 > to > > > ORC 1.6 due to API compatibility. > > > > > > Now, we are more careful at ORC 1.7, but I'm wondering if we have an > > > official policy for Apache ORC versioning. > > > > > > If it's not clear, I'd like to suggest to follow `Semantic Versioning` > in > > > Apache ORC project and to document it in Apache ORC website officially. > > > > > > https://semver.org > > > > > > Bests, > > > Dongjoon. > > > > > >
