Some progress towards this first release, but I’m going to need help — yes,
from YOU! — to get it out of the door.
First the progress report, then some tasks where you can help.
Optiq now has access to Apache’s Nexus repository, and I was able to deploy a
snapshot build to the snapshot repository [1].
To enable that change, I had to change the namespace of our maven artifacts
OPTIQ-354 [2]. The groupId is now “org.apache.optiq”, not
“net.hydromatic.optiq”. And I renamed “optiq-parent” module to “optiq” (the
name has been confusing some people). The full maven coordinates of the
snapshot release are as follows:
<dependency>
<groupId>org.apache.optiq</groupId>
<artifactId>optiq</artifactId>
<version>0.9.0-incubating-SNAPSHOT</version>
</dependency>
optiq/pom.xml now inherits from Apache’s root pom {groupId: “org.apache”,
artifactId: “optiq”, version: “14”}. Repository URLs are in that pom.
The snapshot build proves we can sign jars and push files to Apache, but there
is lots more to do.
Can someone take on OPTIQ-353 [3], and run through the release check list?
We also need a simple web site, OPTIQ-355 [4]. Any volunteers to do that?
There are a few JIRA cases that need to go into this release that should be
suitable for new contributors. Raise your hand and I’ll suggest some.
The code re-org, OPTIQ-296 [5], is frankly going to be a big stretch. Marc has
done a lot of the work, but it is potentially destabilizing. It would be
foolish to commit his patch to master unless the other tasks for the release
are done, and soon. More likely the code re-org will happen right after the
release.
Julian
[1] https://repository.apache.org/content/repositories/snapshots/
[2] https://issues.apache.org/jira/browse/OPTIQ-354
[3] https://issues.apache.org/jira/browse/OPTIQ-353
[4] https://issues.apache.org/jira/browse/OPTIQ-355
[5] https://issues.apache.org/jira/browse/OPTIQ-296
On 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
>>
>>
>>
>
