On another thread we were talking about the names of the reorg packages. Since we're going to hopefully only do this once, I'd like to (re) bring up starting to support a strong delineation between the planning engine and particular data execution code bits.
As far as outstanding patches, I'd like to drive towards a conclusion and merge on DRILL-333 before reorg. I'll respond on that thread separately. On Tue, Jul 8, 2014 at 11:01 AM, Julian Hyde <[email protected]> wrote: > In the discussion threads of > https://issues.apache.org/jira/browse/OPTIQ-336 and > https://issues.apache.org/jira/browse/OPTIQ-296 we are making plans for > the transition, including a big code re-org. If you have forked optiq (or > optiq-csv or linq4j) and have made non-trivial changes, the re-org will > make it extremely difficult to merge. > > If the code re-org affects you, I strongly suggest that you speak up now, > and watch those 2 JIRA cases to hear about further developments. > > If you are using optiq as a client, then you will be affected by the > rename when you upgrade to apache-optiq-0.9-incubating, but we will > document the changes and try to minimize the disruption. > > Julian > > > On Jul 6, 2014, at 1:00 PM, Julian Hyde <[email protected]> wrote: > > > Optiq has been releasing regularly, but it is important that Optiq soon > makes an initial release under the Apache process. > > > > I have logged https://issues.apache.org/jira/browse/OPTIQ-336, "First > Apache release" and intend to drive towards a release 0.9 in the next few > weeks. You will see work towards the release going on on a "stable" branch, > while regular development continues on "master". > > > > Julian > > > > > > > >
