Date   

Re: [DISCUSS] JanusGraph 0.3.2 release

Florian Hockmann <f...@...>
 

I could also move them into an allowed failure group for the time being (my vote).

Agreed, that sounds like the best approach. We don't have to fix everything at once if it was already broken in past releases.

Am Freitag, 14. Juni 2019 01:34:15 UTC+2 schrieb Oleksandr Porunov:
Hello Chris,

Yes, this is the only PR right now for 0.3.2 release. After that I can start a release preparation.
My vote is also to move them into an allowed failure group and making necessary issues for fixing those tests.
In other case we can just move #1601 into the next release milestone.

On Friday, June 14, 2019 at 2:04:51 AM UTC+3, Chris Hupman wrote:
Hey All,

Some of the extended Cassandra tests are failing on the 0.3 branch. Details can be found in PR 1601. I think the tests have been broken since 0.3.0 was released. Based off the milestone this is currently blocking the release. How do we want to proceed? 

I can remove the 2 failing tests from that PR and open an issue to fix the tests in the next release cycle. I could also move them into an allowed failure group for the time being (my vote). Or we could hold up until the tests are fixed.

I spent a few hours this week trying to resolve the failures, but was unsuccessful I don't have the cycles right now to keep digging. I'm hoping we can get the releases moving again. 

Regards,

Chris

On Thursday, May 30, 2019 at 4:18:22 PM UTC-7, Chris Hupman wrote:
I'm out tomorrow, but I was able to get a PR out for the RELEASING.md updates. I plan to look at it again with fresh eyes next week, but I feel like it's ready for feedback.

Also, I think we should wait to merge #1601 until we figure out what's causing the failures in case it can be resolved by updating the test declaration in travis. 

Regards,

Chris

On Thursday, May 30, 2019 at 4:01:54 PM UTC-7, Oleksandr Porunov wrote:
I have reviewed and added #1601 into milestone. We should then figure our why those tests are falling.
I am not sure if #1406 will be fixed soon. If it is then I would like to get it into the release.

Right now the plan is:
- Merge #1601
- Fix tests (or bugs if they are found) which are shown in #1601
- Wait for RELEASING.md update from Chris
- Prepare a release commit

On Thursday, May 30, 2019 at 10:20:34 PM UTC+3, Chris Hupman wrote:
As an FYI. I found some changes in 0.3 that will make my release notes not entirely accurate for the 0.3.2 and 0.4.0 releases. My plan is to open a PR updating RELEASING.md with my notes. I'll do my best to get it out this week, but it might be early next week.

I think you'll want to get #1601 in as well. Right now it shows test failures, but those are for extended tests from travis.yml.cassandra so those failures will need to get addressed in the release. It'll make it easier for you to test out all the Cassandra versions that we claim to support. Rather than doing a separate test in your local branch with the alternate travis config you could just add [full build] to your commit message.

I agree on not including #1547 and #1588. There's some testing going on into whether or not they're still necessary after #1606. The only other possible PR to go in seems like #1406?



On Thursday, May 30, 2019 at 7:49:50 AM UTC-7, Oleksandr Porunov wrote:
Hi everyone,

I am going to make "0.3.2" release PR after conflicts in #1609 is resolved and the PR is merged.
After that I am going to finalize artifacts, docs and start a voting process. 
I have moved all opened issues from "0.3.2" milestone into "v0.3.x" milestone.

I have removed these two issues from milestones: #1547 and #1588 because they look more like features and I am not sure that they will be resolved soon (Of course I will be happy to review them when they are fixed). As I understand we re-targeted them from master into "0.3" because they are partially connected to the bugfix but on the other hand they are introducing a new parameter, so I don't know which branch they should be targeted. I am OK with both "0.3" and "master" branches.

Please, tell if we need to include something else into "0.3.2" release.
Estimated time for starting a release process is 1-2 days.

Best regards,
Oleksandr


Re: [DISCUSS] JanusGraph 0.3.2 release

Oleksandr Porunov <alexand...@...>
 

Hello Chris,

Yes, this is the only PR right now for 0.3.2 release. After that I can start a release preparation.
My vote is also to move them into an allowed failure group and making necessary issues for fixing those tests.
In other case we can just move #1601 into the next release milestone.

On Friday, June 14, 2019 at 2:04:51 AM UTC+3, Chris Hupman wrote:
Hey All,

Some of the extended Cassandra tests are failing on the 0.3 branch. Details can be found in PR 1601. I think the tests have been broken since 0.3.0 was released. Based off the milestone this is currently blocking the release. How do we want to proceed? 

I can remove the 2 failing tests from that PR and open an issue to fix the tests in the next release cycle. I could also move them into an allowed failure group for the time being (my vote). Or we could hold up until the tests are fixed.

I spent a few hours this week trying to resolve the failures, but was unsuccessful I don't have the cycles right now to keep digging. I'm hoping we can get the releases moving again. 

Regards,

Chris

On Thursday, May 30, 2019 at 4:18:22 PM UTC-7, Chris Hupman wrote:
I'm out tomorrow, but I was able to get a PR out for the RELEASING.md updates. I plan to look at it again with fresh eyes next week, but I feel like it's ready for feedback.

Also, I think we should wait to merge #1601 until we figure out what's causing the failures in case it can be resolved by updating the test declaration in travis. 

Regards,

Chris

On Thursday, May 30, 2019 at 4:01:54 PM UTC-7, Oleksandr Porunov wrote:
I have reviewed and added #1601 into milestone. We should then figure our why those tests are falling.
I am not sure if #1406 will be fixed soon. If it is then I would like to get it into the release.

Right now the plan is:
- Merge #1601
- Fix tests (or bugs if they are found) which are shown in #1601
- Wait for RELEASING.md update from Chris
- Prepare a release commit

On Thursday, May 30, 2019 at 10:20:34 PM UTC+3, Chris Hupman wrote:
As an FYI. I found some changes in 0.3 that will make my release notes not entirely accurate for the 0.3.2 and 0.4.0 releases. My plan is to open a PR updating RELEASING.md with my notes. I'll do my best to get it out this week, but it might be early next week.

I think you'll want to get #1601 in as well. Right now it shows test failures, but those are for extended tests from travis.yml.cassandra so those failures will need to get addressed in the release. It'll make it easier for you to test out all the Cassandra versions that we claim to support. Rather than doing a separate test in your local branch with the alternate travis config you could just add [full build] to your commit message.

I agree on not including #1547 and #1588. There's some testing going on into whether or not they're still necessary after #1606. The only other possible PR to go in seems like #1406?



On Thursday, May 30, 2019 at 7:49:50 AM UTC-7, Oleksandr Porunov wrote:
Hi everyone,

I am going to make "0.3.2" release PR after conflicts in #1609 is resolved and the PR is merged.
After that I am going to finalize artifacts, docs and start a voting process. 
I have moved all opened issues from "0.3.2" milestone into "v0.3.x" milestone.

I have removed these two issues from milestones: #1547 and #1588 because they look more like features and I am not sure that they will be resolved soon (Of course I will be happy to review them when they are fixed). As I understand we re-targeted them from master into "0.3" because they are partially connected to the bugfix but on the other hand they are introducing a new parameter, so I don't know which branch they should be targeted. I am OK with both "0.3" and "master" branches.

Please, tell if we need to include something else into "0.3.2" release.
Estimated time for starting a release process is 1-2 days.

Best regards,
Oleksandr


Re: [DISCUSS] JanusGraph 0.3.2 release

Chris Hupman <chris...@...>
 

Hey All,

Some of the extended Cassandra tests are failing on the 0.3 branch. Details can be found in PR 1601. I think the tests have been broken since 0.3.0 was released. Based off the milestone this is currently blocking the release. How do we want to proceed? 

I can remove the 2 failing tests from that PR and open an issue to fix the tests in the next release cycle. I could also move them into an allowed failure group for the time being (my vote). Or we could hold up until the tests are fixed.

I spent a few hours this week trying to resolve the failures, but was unsuccessful I don't have the cycles right now to keep digging. I'm hoping we can get the releases moving again. 

Regards,

Chris


On Thursday, May 30, 2019 at 4:18:22 PM UTC-7, Chris Hupman wrote:
I'm out tomorrow, but I was able to get a PR out for the RELEASING.md updates. I plan to look at it again with fresh eyes next week, but I feel like it's ready for feedback.

Also, I think we should wait to merge #1601 until we figure out what's causing the failures in case it can be resolved by updating the test declaration in travis. 

Regards,

Chris

On Thursday, May 30, 2019 at 4:01:54 PM UTC-7, Oleksandr Porunov wrote:
I have reviewed and added #1601 into milestone. We should then figure our why those tests are falling.
I am not sure if #1406 will be fixed soon. If it is then I would like to get it into the release.

Right now the plan is:
- Merge #1601
- Fix tests (or bugs if they are found) which are shown in #1601
- Wait for RELEASING.md update from Chris
- Prepare a release commit

On Thursday, May 30, 2019 at 10:20:34 PM UTC+3, Chris Hupman wrote:
As an FYI. I found some changes in 0.3 that will make my release notes not entirely accurate for the 0.3.2 and 0.4.0 releases. My plan is to open a PR updating RELEASING.md with my notes. I'll do my best to get it out this week, but it might be early next week.

I think you'll want to get #1601 in as well. Right now it shows test failures, but those are for extended tests from travis.yml.cassandra so those failures will need to get addressed in the release. It'll make it easier for you to test out all the Cassandra versions that we claim to support. Rather than doing a separate test in your local branch with the alternate travis config you could just add [full build] to your commit message.

I agree on not including #1547 and #1588. There's some testing going on into whether or not they're still necessary after #1606. The only other possible PR to go in seems like #1406?



On Thursday, May 30, 2019 at 7:49:50 AM UTC-7, Oleksandr Porunov wrote:
Hi everyone,

I am going to make "0.3.2" release PR after conflicts in #1609 is resolved and the PR is merged.
After that I am going to finalize artifacts, docs and start a voting process. 
I have moved all opened issues from "0.3.2" milestone into "v0.3.x" milestone.

I have removed these two issues from milestones: #1547 and #1588 because they look more like features and I am not sure that they will be resolved soon (Of course I will be happy to review them when they are fixed). As I understand we re-targeted them from master into "0.3" because they are partially connected to the bugfix but on the other hand they are introducing a new parameter, so I don't know which branch they should be targeted. I am OK with both "0.3" and "master" branches.

Please, tell if we need to include something else into "0.3.2" release.
Estimated time for starting a release process is 1-2 days.

Best regards,
Oleksandr


Re: [DISCUSS] JanusGraph 0.4.0 release

Chris Hupman <chris...@...>
 

I agree that #1513, #734, #1540, and #1541 can be added to any release and do not require a major release. Since I'm pretty sure I'm the one that tagged them in the first place I'll move them to 0.4.x. I don't have enough background to really assess #915, but I agree that if it has breaking changes we can just move it to 0.5.0.

Cheers,

Chris

On Friday, June 7, 2019 at 7:26:49 AM UTC-7, Florian Hockmann wrote:
Hi,

now that 0.2.3 is released and 0.3.2 comes closer to a state where it can be released, I want to start the discussion for the 0.4.0 release. It will be a major release with a substantial number of contributions, considering that the last release from master was in October (0.3.1).

Some major new changes in v0.4.0:
  • Upgrade to TinkerPop 3.4.1.
  • Support CQL for OLAP which completes our CQL support.
  • Performance improvements for pre-fetching of properties.
  • Dropped support for deprecated backend versions.
The release milestone can be found here. It currently contains 2 open PRs and 5 issues. The issues are:
  • #915: Support HBase 2.0
  • #1513: Add instructions for opting out from codacy notifications
  • #734: Add systemd unit file
  • #1540: Create noarch rpm spec for rpm creation
  • #1541: Create documentation and scripts to create deb packages
The upgrade to support HBase 2.0 seems to be quite a big task and considering that it has been already 8 months since the last release of JanusGraph from master, I suggest that we don't let this delay the 0.4.0 release. We can just support HBase 2.0 in a subsequent 0.4.x release or release 0.5.0 in a few months if we need a major version bump for this.
The other open issues seem to me like they can basically be addressed in any release. I'm therefore inclined to move them to the v0.4.x milestone so they don't delay any release. If someone provides a PR for one of them shortly, we can still include them in 0.4.0 and otherwise they can land in 0.4.1 or 0.4.2.

My plan is to release 0.4.0 soon after 0.3.2, so I will probably continue with the release preparations when we have a VOTE thread for 0.3.2.

Are there any concerns with this plan? Please share any feedback you might have in general.

Regards,
Florian


[DISCUSS] JanusGraph 0.4.0 release

Florian Hockmann <f...@...>
 

Hi,

now that 0.2.3 is released and 0.3.2 comes closer to a state where it can be released, I want to start the discussion for the 0.4.0 release. It will be a major release with a substantial number of contributions, considering that the last release from master was in October (0.3.1).

Some major new changes in v0.4.0:
  • Upgrade to TinkerPop 3.4.1.
  • Support CQL for OLAP which completes our CQL support.
  • Performance improvements for pre-fetching of properties.
  • Dropped support for deprecated backend versions.
The release milestone can be found here. It currently contains 2 open PRs and 5 issues. The issues are:
  • #915: Support HBase 2.0
  • #1513: Add instructions for opting out from codacy notifications
  • #734: Add systemd unit file
  • #1540: Create noarch rpm spec for rpm creation
  • #1541: Create documentation and scripts to create deb packages
The upgrade to support HBase 2.0 seems to be quite a big task and considering that it has been already 8 months since the last release of JanusGraph from master, I suggest that we don't let this delay the 0.4.0 release. We can just support HBase 2.0 in a subsequent 0.4.x release or release 0.5.0 in a few months if we need a major version bump for this.
The other open issues seem to me like they can basically be addressed in any release. I'm therefore inclined to move them to the v0.4.x milestone so they don't delay any release. If someone provides a PR for one of them shortly, we can still include them in 0.4.0 and otherwise they can land in 0.4.1 or 0.4.2.

My plan is to release 0.4.0 soon after 0.3.2, so I will probably continue with the release preparations when we have a VOTE thread for 0.3.2.

Are there any concerns with this plan? Please share any feedback you might have in general.

Regards,
Florian


Re: Can a TSC member announce the 0.2.3 release in janusgraph-users

Chris Hupman <chris...@...>
 

Announcement sent and I'll add it as a step to the releasing docs. Technically anyone can make an announce thread and the TSC ultimately decides who can add as a release manager. Since the docs weren't totally flushed out and there was a lack of precedent I mainly wanted to verify. 

Just to share, I did some extra searching and found the apache announcing policy. The only tasks that it specifically recommended be done by PMC/TSC members were 1. release manager, and 2. signing artifacts. Both of which I was trusted to do as the release manager. So if anything I was focusing on the wrong gray area. 


On Tuesday, June 4, 2019 at 4:43:23 AM UTC-7, Florian Hockmann wrote:
I think it should be the release manager in general to make the announcement. I don't see a reason why only TSC members should be able to do that if a committer can perform the release itself.

Am Dienstag, 4. Juni 2019 01:10:51 UTC+2 schrieb Chris Hupman:
I may be reading into formality a bit too much with this, but historically releases the releases have been announced on behalf of the technical steering committee. The wording could simply have been based off the fact that the previous 2 release managers were TSC members, but it does seem appropriate for the TSC to make the announcements.

I'm working on updating the release documentation right now and we have the same scenario of a committer as release manager in 0.3.1 so it seems like a good time to iron out this detail.

Regards,

Chris


Re: Can a TSC member announce the 0.2.3 release in janusgraph-users

Florian Hockmann <f...@...>
 

I think it should be the release manager in general to make the announcement. I don't see a reason why only TSC members should be able to do that if a committer can perform the release itself.

Am Dienstag, 4. Juni 2019 01:10:51 UTC+2 schrieb Chris Hupman:

I may be reading into formality a bit too much with this, but historically releases the releases have been announced on behalf of the technical steering committee. The wording could simply have been based off the fact that the previous 2 release managers were TSC members, but it does seem appropriate for the TSC to make the announcements.

I'm working on updating the release documentation right now and we have the same scenario of a committer as release manager in 0.3.1 so it seems like a good time to iron out this detail.

Regards,

Chris


Can a TSC member announce the 0.2.3 release in janusgraph-users

Chris Hupman <chris...@...>
 

I may be reading into formality a bit too much with this, but historically releases the releases have been announced on behalf of the technical steering committee. The wording could simply have been based off the fact that the previous 2 release managers were TSC members, but it does seem appropriate for the TSC to make the announcements.

I'm working on updating the release documentation right now and we have the same scenario of a committer as release manager in 0.3.1 so it seems like a good time to iron out this detail.

Regards,

Chris


Re: [DISCUSS] JanusGraph 0.3.2 release

Chris Hupman <chris...@...>
 

I'm out tomorrow, but I was able to get a PR out for the RELEASING.md updates. I plan to look at it again with fresh eyes next week, but I feel like it's ready for feedback.

Also, I think we should wait to merge #1601 until we figure out what's causing the failures in case it can be resolved by updating the test declaration in travis. 

Regards,

Chris


On Thursday, May 30, 2019 at 4:01:54 PM UTC-7, Oleksandr Porunov wrote:
I have reviewed and added #1601 into milestone. We should then figure our why those tests are falling.
I am not sure if #1406 will be fixed soon. If it is then I would like to get it into the release.

Right now the plan is:
- Merge #1601
- Fix tests (or bugs if they are found) which are shown in #1601
- Wait for RELEASING.md update from Chris
- Prepare a release commit

On Thursday, May 30, 2019 at 10:20:34 PM UTC+3, Chris Hupman wrote:
As an FYI. I found some changes in 0.3 that will make my release notes not entirely accurate for the 0.3.2 and 0.4.0 releases. My plan is to open a PR updating RELEASING.md with my notes. I'll do my best to get it out this week, but it might be early next week.

I think you'll want to get #1601 in as well. Right now it shows test failures, but those are for extended tests from travis.yml.cassandra so those failures will need to get addressed in the release. It'll make it easier for you to test out all the Cassandra versions that we claim to support. Rather than doing a separate test in your local branch with the alternate travis config you could just add [full build] to your commit message.

I agree on not including #1547 and #1588. There's some testing going on into whether or not they're still necessary after #1606. The only other possible PR to go in seems like #1406?



On Thursday, May 30, 2019 at 7:49:50 AM UTC-7, Oleksandr Porunov wrote:
Hi everyone,

I am going to make "0.3.2" release PR after conflicts in #1609 is resolved and the PR is merged.
After that I am going to finalize artifacts, docs and start a voting process. 
I have moved all opened issues from "0.3.2" milestone into "v0.3.x" milestone.

I have removed these two issues from milestones: #1547 and #1588 because they look more like features and I am not sure that they will be resolved soon (Of course I will be happy to review them when they are fixed). As I understand we re-targeted them from master into "0.3" because they are partially connected to the bugfix but on the other hand they are introducing a new parameter, so I don't know which branch they should be targeted. I am OK with both "0.3" and "master" branches.

Please, tell if we need to include something else into "0.3.2" release.
Estimated time for starting a release process is 1-2 days.

Best regards,
Oleksandr


Re: [DISCUSS] JanusGraph 0.3.2 release

Oleksandr Porunov <alexand...@...>
 

I have reviewed and added #1601 into milestone. We should then figure our why those tests are falling.
I am not sure if #1406 will be fixed soon. If it is then I would like to get it into the release.

Right now the plan is:
- Merge #1601
- Fix tests (or bugs if they are found) which are shown in #1601
- Wait for RELEASING.md update from Chris
- Prepare a release commit


On Thursday, May 30, 2019 at 10:20:34 PM UTC+3, Chris Hupman wrote:
As an FYI. I found some changes in 0.3 that will make my release notes not entirely accurate for the 0.3.2 and 0.4.0 releases. My plan is to open a PR updating RELEASING.md with my notes. I'll do my best to get it out this week, but it might be early next week.

I think you'll want to get #1601 in as well. Right now it shows test failures, but those are for extended tests from travis.yml.cassandra so those failures will need to get addressed in the release. It'll make it easier for you to test out all the Cassandra versions that we claim to support. Rather than doing a separate test in your local branch with the alternate travis config you could just add [full build] to your commit message.

I agree on not including #1547 and #1588. There's some testing going on into whether or not they're still necessary after #1606. The only other possible PR to go in seems like #1406?



On Thursday, May 30, 2019 at 7:49:50 AM UTC-7, Oleksandr Porunov wrote:
Hi everyone,

I am going to make "0.3.2" release PR after conflicts in #1609 is resolved and the PR is merged.
After that I am going to finalize artifacts, docs and start a voting process. 
I have moved all opened issues from "0.3.2" milestone into "v0.3.x" milestone.

I have removed these two issues from milestones: #1547 and #1588 because they look more like features and I am not sure that they will be resolved soon (Of course I will be happy to review them when they are fixed). As I understand we re-targeted them from master into "0.3" because they are partially connected to the bugfix but on the other hand they are introducing a new parameter, so I don't know which branch they should be targeted. I am OK with both "0.3" and "master" branches.

Please, tell if we need to include something else into "0.3.2" release.
Estimated time for starting a release process is 1-2 days.

Best regards,
Oleksandr


Re: [DISCUSS] JanusGraph 0.3.2 release

Chris Hupman <chris...@...>
 

As an FYI. I found some changes in 0.3 that will make my release notes not entirely accurate for the 0.3.2 and 0.4.0 releases. My plan is to open a PR updating RELEASING.md with my notes. I'll do my best to get it out this week, but it might be early next week.

I think you'll want to get #1601 in as well. Right now it shows test failures, but those are for extended tests from travis.yml.cassandra so those failures will need to get addressed in the release. It'll make it easier for you to test out all the Cassandra versions that we claim to support. Rather than doing a separate test in your local branch with the alternate travis config you could just add [full build] to your commit message.

I agree on not including #1547 and #1588. There's some testing going on into whether or not they're still necessary after #1606. The only other possible PR to go in seems like #1406?



On Thursday, May 30, 2019 at 7:49:50 AM UTC-7, Oleksandr Porunov wrote:
Hi everyone,

I am going to make "0.3.2" release PR after conflicts in #1609 is resolved and the PR is merged.
After that I am going to finalize artifacts, docs and start a voting process. 
I have moved all opened issues from "0.3.2" milestone into "v0.3.x" milestone.

I have removed these two issues from milestones: #1547 and #1588 because they look more like features and I am not sure that they will be resolved soon (Of course I will be happy to review them when they are fixed). As I understand we re-targeted them from master into "0.3" because they are partially connected to the bugfix but on the other hand they are introducing a new parameter, so I don't know which branch they should be targeted. I am OK with both "0.3" and "master" branches.

Please, tell if we need to include something else into "0.3.2" release.
Estimated time for starting a release process is 1-2 days.

Best regards,
Oleksandr


[DISCUSS] JanusGraph 0.3.2 release

Oleksandr Porunov <alexand...@...>
 

Hi everyone,

I am going to make "0.3.2" release PR after conflicts in #1609 is resolved and the PR is merged.
After that I am going to finalize artifacts, docs and start a voting process. 
I have moved all opened issues from "0.3.2" milestone into "v0.3.x" milestone.

I have removed these two issues from milestones: #1547 and #1588 because they look more like features and I am not sure that they will be resolved soon (Of course I will be happy to review them when they are fixed). As I understand we re-targeted them from master into "0.3" because they are partially connected to the bugfix but on the other hand they are introducing a new parameter, so I don't know which branch they should be targeted. I am OK with both "0.3" and "master" branches.

Please, tell if we need to include something else into "0.3.2" release.
Estimated time for starting a release process is 1-2 days.

Best regards,
Oleksandr


[RESULT][VOTE] JanusGraph 0.2.3 release

Chris Hupman <chris...@...>
 

This vote is now closed with a total of 6 +1s, no +0s and no -1s. The results are:

BINDING VOTES:

+1  (3 -- Jason Plurad,  Florian Hockmann, Alex Patrikalakis)
0   (0)
-1  (0)

NON-BINDING VOTES:

+1 (3 -- Oleksandr Porunov, Chris Human, Jan Jansen)
0  (0)
-1 (0)

Thank you very much,

Chris Hupman


Re: [VOTE] JanusGraph 0.2.3 release

Alexander Patrikalakis <amcpatr...@...>
 

Binding vote +1. Good job on the docker and stability/quality improvements.


On Tuesday, May 21, 2019 at 6:37:24 PM UTC-7, Chris Hupman wrote:
Hello,

We are happy to announce that JanusGraph 0.2.3 is ready for release.

The release artifacts can be found at this location:
        https://github.com/JanusGraph/janusgraph/releases/tag/v0.2.3

A binary distribution is provided for user convenience:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.2.3/janusgraph-0.2.3-hadoop2.zip

The GPG key used to sign the release artifacts is available at:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.2.3/KEYS

The docs can be found here:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.2.3/janusgraph-0.2.3-hadoop2-doc.zip
        (See also documentation preview site)

The release tag in Git can be found here:
        https://github.com/JanusGraph/janusgraph/tree/v0.2.3

Please note that the v0.2.3 tag has been updated. You can refresh your tags with this command:
        git tag -l | xargs git tag -d && git fetch -t

The release notes are available here:
        https://github.com/JanusGraph/janusgraph/blob/v0.2.3/docs/changelog.adoc

This [VOTE] will open for the next 3 days --- closing Friday, May 24, 2018 at 6:45 PM PST.
All are welcome to review and vote on the release, but only votes from TSC members are binding.
My non-binding vote is +1.


Thank you,
Chris Hupman


Re: [VOTE] JanusGraph 0.2.3 release

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

* Imported KEYS file and verified GPG signatures on pre-built distribution files
* Downloaded source code archive and built a distribution
* Unzipped the pre-built distribution and did manual testing with
  * Quick start: Cassandra and Elasticsearch and Gremlin Server
  * BerkeleyJE and Lucene
  * HBase 1.3 and Solr 7.0
* Unzipped the docs and reviewed the formatting

VOTE: +1

Thank you Chris!

On Monday, May 27, 2019 at 3:29:56 AM UTC-4, Jan Jansen wrote:
I just tested to build the docker image for janusgraph and created a PR. The image works perfectly with my changes in PR https://github.com/JanusGraph/janusgraph-docker/pull/17.

My VOTE is +1.


Re: [VOTE] JanusGraph 0.2.3 release

Jan Jansen <faro...@...>
 

I just tested to build the docker image for janusgraph and created a PR. The image works perfectly with my changes in PR https://github.com/JanusGraph/janusgraph-docker/pull/17.

My VOTE is +1.


Re: [VOTE] JanusGraph 0.2.3 release

Chris Hupman <chris...@...>
 

We have 3 +1 votes, however we have only 1 +1 votes from a TSC member, which falls short of the 3 required for the release.

Chris Hupman
Oleksandr Porunov
Florian Hockmann *

* denotes TSC member

Due to the holiday weekend I'm going to extend the until Wednesday, May 29, 2019 at 4:00 PM PDT

If there are any concerns with this approach, please reply on this thread. Thank you.


On Thursday, May 23, 2019 at 11:24:17 AM UTC-7, Oleksandr Porunov wrote:
I have downloaded .tar.zip, extracted it, built jars, included into my personal project with different integration tests. Ran integration tests. All tests have passed except some tests which require the fix #1501.
As this bug wasn't introduced in `0.2.3` and currently it is placed in all janusgraph versions (except current `0.3` and `master`) then I think it is OK.

My VOTE is +1.  

On Thursday, May 23, 2019 at 5:07:37 PM UTC+3, Florian Hockmann wrote:
I skimmed over the docs and everything looks as expected.
The changelog and the release on GitHub also look good.
I also downloaded the zip archive, extracted it, started JanusGraph with bin/janusgraph.sh and loaded a toy graph created with 0.2.2. Then I executed some example traversals and didn't run into any problems.

My VOTE is +1.

Am Mittwoch, 22. Mai 2019 22:31:05 UTC+2 schrieb Chris Hupman:
Thanks for catching that. It's been updated.

On Wed, May 22, 2019 at 12:58 PM Oleksandr Porunov <ale...@...> wrote:
Hello Chris,


It says: Version 0.2.2 (October 9, 2018)
I assume it should be: Version 0.2.3 (May 21, 2019)

On Wednesday, May 22, 2019 at 4:37:24 AM UTC+3, Chris Hupman wrote:
Hello,

We are happy to announce that JanusGraph 0.2.3 is ready for release.

The release artifacts can be found at this location:
        https://github.com/JanusGraph/janusgraph/releases/tag/v0.2.3

A binary distribution is provided for user convenience:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.2.3/janusgraph-0.2.3-hadoop2.zip

The GPG key used to sign the release artifacts is available at:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.2.3/KEYS

The docs can be found here:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.2.3/janusgraph-0.2.3-hadoop2-doc.zip
        (See also documentation preview site)

The release tag in Git can be found here:
        https://github.com/JanusGraph/janusgraph/tree/v0.2.3

Please note that the v0.2.3 tag has been updated. You can refresh your tags with this command:
        git tag -l | xargs git tag -d && git fetch -t

The release notes are available here:
        https://github.com/JanusGraph/janusgraph/blob/v0.2.3/docs/changelog.adoc

This [VOTE] will open for the next 3 days --- closing Friday, May 24, 2018 at 6:45 PM PST.
All are welcome to review and vote on the release, but only votes from TSC members are binding.
My non-binding vote is +1.


Thank you,
Chris Hupman

--
You received this message because you are subscribed to a topic in the Google Groups "JanusGraph developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/janusgraph-dev/ndOUqZ8sC5g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jan...@....
To post to this group, send email to jan...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/d39d69ac-f940-4ee3-b57f-908f8171bf9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [DISCUSS] Support of CQL backend for Spark #985

Florian Hockmann <f...@...>
 

I think that we should not remove support for Thrift for 0.4.0 as we only gain full support for the successor CQL in 0.4.0 with the added support for Spark (PR #1436). I think we should first deprecate Thrift in a following 0.4.z version, assuming that CQL doesn't introduce bigger problems.
Then we can drop support for Thrift completely in 0.5.0 and update to Cassandra 3.

We should probably target a release date relatively soon for 0.5.0 as Cassandra 2.2 will be EOL once Cassandra 4 comes out and Cassandra 3 will also only be supported 6 months after that (source). Since we already have a PR for an improved inmemory storage backend that should probably also not be introduced in a patch version, it makes sense in general to start working on 0.5.0 soon.

Am Freitag, 24. Mai 2019 00:27:14 UTC+2 schrieb Chris Hupman:

I was looking into libthrift again and realized I did a bad job keeping up with us. Were most of the issues figured out in PR 1400 and PR 1436? What else is there to do before we can remove libthrift as a dependency in 0.4.0? 

On Wednesday, January 23, 2019 at 1:56:54 AM UTC-8, Florian Hockmann wrote:
but I do wonder how long we should continue to support things like thrift and upgrading from titan.

I think we should deprecate Thrift soon and then remove it in the next minor version of JanusGraph after that, but we probably need to offer the same functionality for CQL as for Thrift before we can deprecate Thrift. Since we currently don't support Spark without Thrift, we can't really deprecate it yet in my opinion. Another issue we may want to take into account when talking about deprecation / removal of Thrift is the reported performance decrease of CQL compared to Thrift: JanusGraph/janusgraph#1249

Now regarding, how to support CQL for Spark: I found out in the meantime that Cassandra removed all Thrift code from its CQL components already in version 2.2 with CASSANDRA-8358. This most likely means for us that we only have to update to Cassandra 2.2 to get full CQL support for Spark which also means that we don't have to do anything about Thrift right now as Thrift is still fully supported in Cassandra 2.2. We only have to decide about that when we actually update to Cassandra 3.0, but we can do that at a later point (ideally before Cassandra 4.0 will be released as support for Cassandra 2.1 and 2.2 will end with that release).

The current state of this work is that the update to Cassandra 2.2 led to build failures where I have no idea yet what's causing them. janusgraph-solr and some other projects that all depend on janusgraph-cassandra now fail with this error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.15:integration-test (default) on project janusgraph-solr: Execution default of goal
org
.apache.maven.plugins:maven-failsafe-plugin:2.15:integration-test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?

This commit introduced the problem. I found a lot of reports with similar problems, but none of the suggested solutions helped so far. It's also strange that janusgraph-cassandra itself doesn't fail with this error.

I already created a branch that includes the update to Cassandra 2.2 and an initial version of a CQL input format for Spark, but for some reason my tests aren''t executed:

Running org.janusgraph.hadoop.CqlInputFormatIT
SLF4J
: Class path contains multiple SLF4J bindings.
SLF4J
: Found binding in [jar:file:/home/travis/.m2/repository/org/slf4j/slf4j-log4j12/1.7.12/slf4j-log4j12-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J
: Found binding in [jar:file:/home/travis/.m2/repository/ch/qos/logback/logback-classic/1.1.3/logback-classic-1.1.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J
: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J
: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
Running org.janusgraph.hadoop.CassandraInputFormatIT

If anyone here has any helpful input on one of these two problems, then I would really appreciate that as I'm starting to run out of ideas here...

Am Mittwoch, 23. Januar 2019 03:44:40 UTC+1 schrieb Chris Hupman:
+1 for number 3.

Number 3 is probably the best option, but I do wonder how long we should continue to support things like thrift and upgrading from titan. 

On Wednesday, January 9, 2019 at 3:02:50 AM UTC-8, Florian Hockmann wrote:
Hi,
Jan Jansen (farodin91) and I took a first try at implementing a CQL input format for Spark to enable OLAP jobs to work without Thrift (#985). Unfortunately, we can't just add wrappers for the CQL OLAP support in org.apache.cassandra and be done with it. The reason is that JanusGraph still uses version 2.1.20 of org.apache.cassandra cassandra-all which is not compatible with the version of the DataStax Cassandra driver JanusGraph is using. So, we need to update the org.apache.cassandra dependency to major version 3.
With this update we would however lose support for Thrift as that was thrown out completely in version 3.0.0 (see CASSANDRA-9353). That leaves us with the following options:
  1. Update the dependency and drop support for Thrift. Thrift is deprecated since Cassandra 3.0 which was released in November 2015. Users who want to continue using Thrift could stay on a JanusGraph version that still supports it.
  2. Create a separate project janusgraph-hadoop-cql that can use newer versions of these two dependencies without affecting the Thrift support in janusgraph-hadoop-core.
  3. Update the dependency and include the classes for Thrift support from org.apache.cassandra.hadoop package in janusgraph-hadoop-core.
The first option would of course be the easiest to implement and I think that dropping support for Thrift over 3 years after deprecation started and only in a new major release of JanusGraph would be acceptable. However, this comes with some risk as we would make CQL the only way to use OLAP with Cassandra in the same version in which we introduce the CQL OLAP support. So, if we find any problems with the implementation, then users could only downgrade to a lower version of JanusGraph that still supports Thrift as there wouldn’t be an alternative input format left.
We should probably update the dependency at some point irrespective of the support for CQL any way so creating a new project now just to not update the dependency in janusgraph-hadoop-core probably isn’t the best idea.
That is why option 3 sounds like the best one to us. We would add support for OLAP with CQL without losing support for Thrift which we could drop at any time in the future.

Any thoughts or other opinions on this topic?


Re: [DISCUSS] Support of CQL backend for Spark #985

Chris Hupman <chris...@...>
 

I was looking into libthrift again and realized I did a bad job keeping up with us. Were most of the issues figured out in PR 1400 and PR 1436? What else is there to do before we can remove libthrift as a dependency in 0.4.0? 


On Wednesday, January 23, 2019 at 1:56:54 AM UTC-8, Florian Hockmann wrote:
but I do wonder how long we should continue to support things like thrift and upgrading from titan.

I think we should deprecate Thrift soon and then remove it in the next minor version of JanusGraph after that, but we probably need to offer the same functionality for CQL as for Thrift before we can deprecate Thrift. Since we currently don't support Spark without Thrift, we can't really deprecate it yet in my opinion. Another issue we may want to take into account when talking about deprecation / removal of Thrift is the reported performance decrease of CQL compared to Thrift: JanusGraph/janusgraph#1249

Now regarding, how to support CQL for Spark: I found out in the meantime that Cassandra removed all Thrift code from its CQL components already in version 2.2 with CASSANDRA-8358. This most likely means for us that we only have to update to Cassandra 2.2 to get full CQL support for Spark which also means that we don't have to do anything about Thrift right now as Thrift is still fully supported in Cassandra 2.2. We only have to decide about that when we actually update to Cassandra 3.0, but we can do that at a later point (ideally before Cassandra 4.0 will be released as support for Cassandra 2.1 and 2.2 will end with that release).

The current state of this work is that the update to Cassandra 2.2 led to build failures where I have no idea yet what's causing them. janusgraph-solr and some other projects that all depend on janusgraph-cassandra now fail with this error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.15:integration-test (default) on project janusgraph-solr: Execution default of goal
org
.apache.maven.plugins:maven-failsafe-plugin:2.15:integration-test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?

This commit introduced the problem. I found a lot of reports with similar problems, but none of the suggested solutions helped so far. It's also strange that janusgraph-cassandra itself doesn't fail with this error.

I already created a branch that includes the update to Cassandra 2.2 and an initial version of a CQL input format for Spark, but for some reason my tests aren''t executed:

Running org.janusgraph.hadoop.CqlInputFormatIT
SLF4J
: Class path contains multiple SLF4J bindings.
SLF4J
: Found binding in [jar:file:/home/travis/.m2/repository/org/slf4j/slf4j-log4j12/1.7.12/slf4j-log4j12-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J
: Found binding in [jar:file:/home/travis/.m2/repository/ch/qos/logback/logback-classic/1.1.3/logback-classic-1.1.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J
: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J
: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
Running org.janusgraph.hadoop.CassandraInputFormatIT

If anyone here has any helpful input on one of these two problems, then I would really appreciate that as I'm starting to run out of ideas here...

Am Mittwoch, 23. Januar 2019 03:44:40 UTC+1 schrieb Chris Hupman:
+1 for number 3.

Number 3 is probably the best option, but I do wonder how long we should continue to support things like thrift and upgrading from titan. 

On Wednesday, January 9, 2019 at 3:02:50 AM UTC-8, Florian Hockmann wrote:
Hi,
Jan Jansen (farodin91) and I took a first try at implementing a CQL input format for Spark to enable OLAP jobs to work without Thrift (#985). Unfortunately, we can't just add wrappers for the CQL OLAP support in org.apache.cassandra and be done with it. The reason is that JanusGraph still uses version 2.1.20 of org.apache.cassandra cassandra-all which is not compatible with the version of the DataStax Cassandra driver JanusGraph is using. So, we need to update the org.apache.cassandra dependency to major version 3.
With this update we would however lose support for Thrift as that was thrown out completely in version 3.0.0 (see CASSANDRA-9353). That leaves us with the following options:
  1. Update the dependency and drop support for Thrift. Thrift is deprecated since Cassandra 3.0 which was released in November 2015. Users who want to continue using Thrift could stay on a JanusGraph version that still supports it.
  2. Create a separate project janusgraph-hadoop-cql that can use newer versions of these two dependencies without affecting the Thrift support in janusgraph-hadoop-core.
  3. Update the dependency and include the classes for Thrift support from org.apache.cassandra.hadoop package in janusgraph-hadoop-core.
The first option would of course be the easiest to implement and I think that dropping support for Thrift over 3 years after deprecation started and only in a new major release of JanusGraph would be acceptable. However, this comes with some risk as we would make CQL the only way to use OLAP with Cassandra in the same version in which we introduce the CQL OLAP support. So, if we find any problems with the implementation, then users could only downgrade to a lower version of JanusGraph that still supports Thrift as there wouldn’t be an alternative input format left.
We should probably update the dependency at some point irrespective of the support for CQL any way so creating a new project now just to not update the dependency in janusgraph-hadoop-core probably isn’t the best idea.
That is why option 3 sounds like the best one to us. We would add support for OLAP with CQL without losing support for Thrift which we could drop at any time in the future.

Any thoughts or other opinions on this topic?


Re: [VOTE] JanusGraph 0.2.3 release

Oleksandr Porunov <alexand...@...>
 

I have downloaded .tar.zip, extracted it, built jars, included into my personal project with different integration tests. Ran integration tests. All tests have passed except some tests which require the fix #1501.
As this bug wasn't introduced in `0.2.3` and currently it is placed in all janusgraph versions (except current `0.3` and `master`) then I think it is OK.

My VOTE is +1.  


On Thursday, May 23, 2019 at 5:07:37 PM UTC+3, Florian Hockmann wrote:
I skimmed over the docs and everything looks as expected.
The changelog and the release on GitHub also look good.
I also downloaded the zip archive, extracted it, started JanusGraph with bin/janusgraph.sh and loaded a toy graph created with 0.2.2. Then I executed some example traversals and didn't run into any problems.

My VOTE is +1.

Am Mittwoch, 22. Mai 2019 22:31:05 UTC+2 schrieb Chris Hupman:
Thanks for catching that. It's been updated.

On Wed, May 22, 2019 at 12:58 PM Oleksandr Porunov <ale...@...> wrote:
Hello Chris,


It says: Version 0.2.2 (October 9, 2018)
I assume it should be: Version 0.2.3 (May 21, 2019)

On Wednesday, May 22, 2019 at 4:37:24 AM UTC+3, Chris Hupman wrote:
Hello,

We are happy to announce that JanusGraph 0.2.3 is ready for release.

The release artifacts can be found at this location:
        https://github.com/JanusGraph/janusgraph/releases/tag/v0.2.3

A binary distribution is provided for user convenience:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.2.3/janusgraph-0.2.3-hadoop2.zip

The GPG key used to sign the release artifacts is available at:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.2.3/KEYS

The docs can be found here:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.2.3/janusgraph-0.2.3-hadoop2-doc.zip
        (See also documentation preview site)

The release tag in Git can be found here:
        https://github.com/JanusGraph/janusgraph/tree/v0.2.3

Please note that the v0.2.3 tag has been updated. You can refresh your tags with this command:
        git tag -l | xargs git tag -d && git fetch -t

The release notes are available here:
        https://github.com/JanusGraph/janusgraph/blob/v0.2.3/docs/changelog.adoc

This [VOTE] will open for the next 3 days --- closing Friday, May 24, 2018 at 6:45 PM PST.
All are welcome to review and vote on the release, but only votes from TSC members are binding.
My non-binding vote is +1.


Thank you,
Chris Hupman

--
You received this message because you are subscribed to a topic in the Google Groups "JanusGraph developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/janusgraph-dev/ndOUqZ8sC5g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jan...@....
To post to this group, send email to jan...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/d39d69ac-f940-4ee3-b57f-908f8171bf9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

481 - 500 of 1601