Actually, I found out that there are complications with having to document
difference in two versions of binary release.
Since getting the release is a bigger priority, I'll go with the default
(2.11 dependencies) and push back providing two versions to next release,
if deemed necessary then.
On
That sounds great. I'll prepare a new RC with updates and binary
distribution.
I think it would be reasonable to provide two binary distributions: (Scala
2.10.6 / Spark 1.6.3 / ES 1.7.3), (Scala 2.11.8 / Spark 2.1.1 / ES 5.5.2).
Does anyone have objections?
On Sat, Sep 16, 2017 at 2:24 PM, Mars
That should be fine. Chan, the binary distribution package should be
treated the same as what we are doing with publishing Maven artifacts
(classified as convenience binaries by ASF). Instead of going to Nexus,
they need to go alongside the source (i.e. SVN). We will similarly need to
produce PGP
Sorry I didn't catch this before RC1. Thank you Chan.
On Fri, Sep 15, 2017 at 12:35 PM, Chan Lee wrote:
> Mars, this seems like a necessary change, so I'll create RC3 with the PR
> and additional updates here: http://predictionio.incubator.apache.org/
> resources/upgrade/
Mars, this seems like a necessary change, so I'll create RC3 with the PR
and additional updates here: http://predictionio.incubator.apache.org/
resources/upgrade/
If there are changes anyone would like to add, please let me know by today.
I'll patch up another release tonight and send out a new
Votes are tied to tag/commit by ASF convention, so a new RC and vote will
be required.
On Fri, Sep 15, 2017 at 10:57 AM Mars Hall wrote:
> I just opened a release notes PR against apache:release/0.12.0, because
> that seems to be the right place.
>
> Chan, will that
I just opened a release notes PR against apache:release/0.12.0, because
that seems to be the right place.
Chan, will that work okay with the release process?
On Fri, Sep 15, 2017 at 10:20 AM, Mars Hall
wrote:
> Also, I'd love to directly link the PIO-* issue numbers
RC2 is working perfectly.
I see a few issues with the releases notes:
- PIO-95 should be "Raised request timeout for REST API to 35-seconds"
- PIO-102, PIO-106, PIO-117, PIO-118, PIO-120 actually includes a
breaking change to Elasticsearch 5.x StorageClient interface. I think these
I believe those are fixed by PIO-60, PIO-62 and PIO-63 in the release notes.
+1 binding from me
On Thu, Sep 14, 2017 at 2:13 PM Pat Ferrel wrote:
> The last release was hung up by the IPMC regarding content licensing
> issues and libraries used by the doc site, which we
The last release was hung up by the IPMC regarding content licensing issues and
libraries used by the doc site, which we promised to address in this release.
Have these been resolved, don’t recall the specifics? It would be great to fly
through the IPMC vote without issue.
On Sep 14, 2017, at
10 matches
Mail list logo