Re: [DISCUSS] Release planning v0.3.0

Jason Plurad <plu...@...>

Things are shaping up on the Release v0.3.0 milestone. Committers, if you have a time to review/approve some of these outstanding PRs, that would be fantastic.

There are also a couple other PRs that are close to complete but could use some help moving along: PR 961 and PR 362.

Jerry He is planning to contribute support for the recent HBase 2.0 release. And similar to the upcoming JanusGraph 0.2.1 release, I think it's best at this point to hold out for the quick patch release 3.3.3, with release expected week of May 7.


On Monday, April 2, 2018 at 12:48:47 PM UTC-4, Jason Plurad wrote:
Let's start a discussion on releases. This thread is for the master branch (0.3.0 release).

The master branch has fixes and new features. The master branch is currently based on Apache TinkerPop 3.3.1 which uses Spark 2.2.0 and Scala 2.11.

Apache TinkerPop 3.3.2 is in [code freeze](, so it will be out very soon. We'd want to align JanusGraph 0.3.0 with that latest version. We're waiting on TinkerPop 3.3.2 to resolve [#859](

I've tagged all the pull requests that are slated for 0.3.0 with milestone "Release v0.3.0"
- [Pull requests]( 5 open, 69 closed
- [Closed issues]( 33 closed (plus the 28 issues closed against v0.2.1)

A few significant changes for v0.3.0:
- TinkerPop 3.3.z, Spark 2.2.0, Scala 2.11 [#705](
- Elasticsearch authentication/SSL support [#612](
- JanusGraph Authentication for Gremlin Server [#623](
- JanusGraph OLAP with HBase TableSnapshotInputFormat [#656](
- Custom analyzer for Lucene [#672](
- Many documentation fixes

I think we can make a concerted effort this week to close out the remaining [open pull requests]( targeted for master. Once the merges are complete, we can start release preparation for 0.3.0. Any open issues that don't have a pull request merged before the cut off will be moved along to the next release.

I volunteer to be the release manager.

Is anybody working on fixes for 0.3 that you're planning to submit a PR this week?

Join { to automatically receive all group messages.