OTp20 riak3 meeting agenda

agenda

Some possible agenda points:

- Starting point for work (ted branchen? Basho develop? 2.2???)
- existing work ( Ted got about 80% through this work once, and there exists riak_core_ng)
- backwards compatibility
- assigning work, processes and coordination (many hands make light work, but too many cooks etc)
- testing and coverage and confidence (are we sure this change has no semantic impact? Is this code even tested?)
- Riak_test or CT or wat? (related to above)
- Etc?

Below is the list of repos with "rebar3" branches from my notes, with version notations, as of maybe last March-ish.
There are a couple more that are essentially done but not on a top-level "rebar3" branch.
I've only just started fiddling with the code again, and I've never run it through the unit tests on OTP-20 GA (though I don't expect any problems there).

%   {cuttlefish,        {branch, "rebar3"}},    % √ 16-20
%   {basho_stats,       {branch, "rebar3"}},    % √ 16-20
%   {bear,              {branch, "rebar3"}},    % √ 16-20
%   {clique,            {branch, "rebar3"}},    % √ 16-20
%   {cluster_info,      {branch, "rebar3"}},    % √ 16-20
%   {edown,             {branch, "rebar3"}},    % √ 16-20
%   {eleveldb,          {branch, "rebar3"}},    % √ 16-20
%   {exometer_core,     {branch, "rebar3"}},    % √ 16-20
%   {folsom,            {branch, "rebar3"}},    % √ 16-18   QC fudged, OTP-19+ eunit crash
%   {getopt,            {branch, "rebar3"}},    % √ 16-20
%   {goldrush,          {branch, "rebar3"}},    % √ 16-20
%   {hamcrest,          {branch, "rebar3"}},    % √ 16-20
%   {lager,             {branch, "rebar3"}},    % √ 16-19   OTP-20 errors
%   {meck,              {branch, "rebar3"}},    % √ 16-20
%   {neotoma,           {branch, "rebar3"}},    % √ 16-20
%   {parse_trans,       {branch, "rebar3"}},    % √ 16-20
%   {pbkdf2,            {branch, "rebar3"}},    % √ 16-20
%   {rand_compat,       {branch, "rebar3"}},    % not using
%   {riak_core,         {branch, "rebar3"}},    % √ 16-20
%   {riak_ensemble,     {branch, "rebar3"}},    % √ 16-20
%   {riak_sysmon,       {branch, "rebar3"}},    % √ 16-20
%   {setup,             {branch, "rebar3"}},    % √ 16-20
%   {chronos,           {branch, "rebar3"}},    % √ 16-20
%   {hyper,             {branch, "basho"}},     % √ 16-20
%   {sext,              {branch, "rebar3"}},    % √ 16-20
%   {canola,            {branch, "rebar3"}},    % √ 16-20

btw, I've started twiddling here: https://github.com/rebar3riak

@tburghart I'd heard about these, like in @russelldb's agenda points, but had no idea there were so many. I'd just looked in branches for "otp", never noticed the rebar3 ones (doh!). Awesome starting point 👍

except what branch are they based on? develop? 2.2?

not sure if 1 or 2 pre-releases/release-candidates of 3.0 (3.0-rc-1 & 3.0-rc-2 perhaps?) with the number of possible breaking changes, in performance as well, which users can try out before the official launch of 3.0?

notes:
1 . take what Ted has done as a starting point
2. what Ted hasn't done work on riak-2.2 repos
3. do not have backwards compat work going forward
4. martin cox to add simple work coord page to riak repo
5. porting riak test to CT whatever is another battle
6. meet 1st wed of the month next month for progress