Re: Slack (was: Re: Deprecation of Riak SNMP and Riak JMX?)

To not include them in the open-source release. > On 13 Nov 2017, at 16:00, martin@bet365.com wrote: > > I'm in support of deprecating. Is the intention to include them in the > open-source release, only to remove them in the following release? May as > well not include them to start with,

Re: Slack (was: Re: Deprecation of Riak SNMP and Riak JMX?)

Here is the invite link; https://join.slack.com/t/postriak/shared_invite/enQtMjcyMjkyNzAyMDM4LTM2YzQxMTUzMDhlZDQ1ZGYzZDk4NDVlMzM2Njc1OGVjZTdmNTU3YThkY2VhMGFlODlkN2YzZmMxZGM3YTM5ZDA On Mon, Nov 13, 2017 at 6:55 PM, Christopher Meiklejohn wrote: > +1, same. > > On Mon, Nov 13, 2017 at 4:54 P

Re: Slack (was: Re: Deprecation of Riak SNMP and Riak JMX?)

+1, same. On Mon, Nov 13, 2017 at 4:54 PM Jean Parpaillon wrote: > Hi, > Speaking about slack, is it possible to have an invitation ? > > Jean > > Le lundi 13 novembre 2017 à 15:50 +, Bryan Hunt a écrit : > > Already discussed on Slack but just to be public: > > > > I’m in favour of keeping

Slack (was: Re: Deprecation of Riak SNMP and Riak JMX?)

Hi, Speaking about slack, is it possible to have an invitation ? Jean Le lundi 13 novembre 2017 à 15:50 +, Bryan Hunt a écrit : > Already discussed on Slack but just to be public: > > I’m in favour of keeping the repositories around but not including > them as Riak dependencies or supporting

Re: Deprecation of Riak SNMP and Riak JMX?

Already discussed on Slack but just to be public: I’m in favour of keeping the repositories around but not including them as Riak dependencies or supporting them going forward. Any others ? > On 13 Nov 2017, at 10:48, Russell Brown wrote: > > Hi all, > It looks like we’re moving toward shippi

Re: OTP migration

Ted Burghart did a lot of this work already. It would be great if we could re-use some of the work. He talks about it here - http://www.erlang-factory.com/sfbay2017/ted-burghart.html The NHS commissioned a report on this work a while back, and I’ll ask and see if they are willing to share it.

Re: OTP migration

Done. > On 13 Nov 2017, at 12:10, Jean Parpaillon wrote: > > Hi Bryan, > The wiki page and tickets have been created on purpose, as I've guessed many > work has already been done here and there and the hardest part is now to > integrate it :) > > -> can you add a line in the wiki page: > ht

Re: OTP migration

Hi Bryan,The wiki page and tickets have been created on purpose, as I've guessed many work has already been done here and there and the hardest part is now to integrate it :) -> can you add a line in the wiki page: https://github.com/basho/riak/w iki/OTP-migration-task-follow-up ? Jean Le lundi 13

Re: OTP migration

To get the ball rolling, I’ve got a very low risk p/r for riak-erlang-client to enable Erlang 20 support. Would be great to get it merged in. https://github.com/basho/riak-erlang-client/pull/367 > On 13 Nov 2017, at 11:17, Jean Parpaill

Re: OTP migration

Heinz (and Tristan, and myself) have done a bunch of work on his fork of Riak Core (and, Ensemble, and a few other libraries) to bring them up to the latest OTP. I know at least the Antidote folks, Lasp folks, Project FIFO, and Partisan folks have used these as starting points for their work. It

OTP migration

Hi all, As announced during the meetup, at KBRW we want to help on the OTP migration task. IIRC, the migration is targeted for post 2.2.5 release, as to not postpone this release. As suggested by Russell, we're starting from nhs-riak-2.2.5 branch. I've opened a ticket for following-up our work on

Deprecation of Riak SNMP and Riak JMX?

Hi all, It looks like we’re moving toward shipping the open source repl code with the next release of Riak. I’m canvassing for opinions about the riak_snmp and riak_jmx portions of the enterprise code. Is there anyone out there that depends on these features? I’d like to deprecate them in the n