russell.brown at icloud.com
Wed Oct 25 04:55:23 EDT 2017
TL:DR - https://github.com/nhs-riak/riak/tree/rdb/nhs-riak-2.2.5 is the fork/branch that I’ve been making progress on.
From my understanding of what we discussed, or at least my view: in order that we generate momentum and show signs of life, the best thing to do is release a new Riak, but a low risk Riak. Based on that, we (NHS) thought take the last known good release (riak-2.2.3) and branch of that. Use it as a basis for some low risk features/fixes and release it soon. The aim was this year, or at latest January 2018. That release would contain some NHS features, a fix for claim, G-Sets, and maybe some AAE fullsync repl fixes. I have been working on the NHS fork for this for a while. My initial aim has been so that a developer can clone Riak, and run `make test`, and it will pass. Next is to make riak-test pass. Set up CI. Then add in the new features already fixed, and finally build and release. Then there should be a reasonably low-risk, community Riak-2.2.5 for us to deploy. After, we build on that for the more risky work (OTP20, etc etc.)
The fork I’ve been working off is https://github.com/nhs-riak/riak. The branch that one should be able to build is nhs-riak-2.2.5 (https://github.com/nhs-riak/riak/tree/rdb/nhs-riak-2.2.5). Cloning https://github.com/nhs-riak/riak.git and then `git checkout nhs-riak-2.2.5` and then `make test` should work. Though I have one or two test failures still on linux (not on OS X afaict.)
Each of the deps that I had to change in order to get the build working is also forked in the https://github.com/nhs-riak/ organisation. Each dependancy's branch is named after the last released tag + “nhs-2.2.5”. For example, https://github.com/nhs-riak/riak_kv has branch 2.1.7-nhs-2.2.5 (since 2.1.7 was the last released tag.) When it all works the plan was to push each new branch to the canonical basho organisation and name it develop-2.2.5 (or something) and from there we can work towards the next release (and the one after, maybe a develop-3.0 branch based off 2.2.5.) We also sidestep the issue of reviewing and fixing up all of the basho unreleased dev code, which we can cherry-pick as we need.
I don’t know if this is the best idea, but it seems like a pragmatic approach to building momentum and getting something of value released, as well as setting us up for longer term improvements.
It is sort of what we agreed at the meet-up, but I’d love to hear views from the wider community.
On 25 Oct 2017, at 10:28, Jean Parpaillon <jean.parpaillon at free.fr> wrote:
> Hi Andrew, all,
> IIRC, we have mentioned an important step to bootstrap the community is to identify baselines.
> Can anyone confirm that contributions should be based on NHS branch (which one ?) ? In particular, I'm interested in contributing to OTP19/20 upgrade.
> Furthermore, I've mentioned OW2 organization would be glad to provide the community with infrastructure: gitlab, CI (tools + servers), etc.
> Are you interested in it ? Just let me know if it is the case or have a look at the project submission page:https://projects.ow2.org/bin/view/wiki/submission#
> Best regards,
> Le mardi 24 octobre 2017 à 10:32 +0000, Andrew.Deane at bet365.com a écrit :
>> A summary of the RIAK Development Roadmap Workshop can be found here http://bet365techblog.com/riak-workshop-summary
>> Andrew Deane
>> Systems Development Manager - Middleware
>> Hillside (Technology) Limited
>> andrew.deane at bet365.com
>> This email and any files transmitted with it are confidential and contain information which may be privileged or confidential and are intended solely to be for the use of the individual(s) or entity to which they are addressed. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited and may be illegal. If you have received this email in error, please notify us by telephone or email immediately and delete it from your system. Activity and use of our email system is monitored to secure its effective operation and for other lawful business purposes. Communications using this system will also be monitored and may be recorded to secure effective operation and for other lawful business purposes. Internet emails are not necessarily secure. We do not accept responsibility for changes made to this message after it was sent. You are advised to scan this message for viruses and we cannot accept liability for any loss or damage which may be caused as a result of any computer virus.
>> This email is sent by a bet365 group entity. The bet365 group includes the following entities: Hillside (Shared Services) Limited (registration no. 3958393), Hillside (Spain New Media) Plc (registration no. 07833226), bet365 Group Limited (registration no. 4241161), Hillside (Technology) Limited (registration no. 8273456), Hillside (Media Services) Limited (registration no. 9171710), Hillside (Trader Services) Limited (registration no. 9171598) each registered in England and Wales with a registered office address at bet365 House, Media Way, Stoke-on-Trent, ST1 5SZ, United Kingdom; Hillside (Gibraltar) Limited (registration no. 97927), Hillside (Sports) GP Limited (registration no. 111829) and Hillside (Gaming) GP Limited (registered no. 111830) each registered in Gibraltar with a registered office address at Unit 1.1, First Floor, Waterport Place, 2 Europort Avenue, Gibraltar; Hillside (UK Sports) LP (registration no. 117), Hillside (Sports) LP (registration no. 118), Hillside (International Sports) LP (registration no. 119), Hillside (Gaming) LP (registration no. 120) and Hillside (International Gaming) LP (registration no. 121) each registered in Gibraltar with a principal place of business at Unit 1.1, First Floor, Waterport Place, 2 Europort Avenue, Gibraltar; Hillside España Leisure S.A (CIF no. A86340270) registered in Spain with a registered office address at C/ Conde de Aranda nº20, 2º, 28001 Madrid, Spain; Hillside (Australia New Media) Pty Limited (registration no. 148 920 665) registered in Australia with a registered office address at Level 4, 90 Arthur Street, North Sydney, NSW 2060, Australia; Hillside (New Media Malta) Plc, (registration no c.66039) registered in Malta with a registered office address at Office 1/2373, Level G, Quantum House, 75 Abate Rigord Street, Ta’ Xbiex XBX 1120, Malta and Hillside (New Media Cyprus) Limited, (registration no. HE 361612) registered in Cyprus with a registered office address at Omrania Centre, 313, 28th October Avenue, 3105 Limassol, Cyprus. Hillside (Shared Services) Limited, Hillside (Spain New Media) Plc and Hillside (New Media Malta) Plc also have places of business at Unit 1.1, First Floor, Waterport Place, 2 Europort Avenue, Gibraltar. For residents of Greece, this email is sent on behalf of B2B Gaming Services (Malta) Limited (registration number C41936) organised under the laws of Malta with a registered office at Apartment 21, Suite 41, Charles Court, St. Luke's Road, Pietà, Malta.
>> riak-users mailing list
>> riak-users at lists.basho.com
> Jean Parpaillon
> Senior Developper @ KBRW Adventure
> Chairman @ OW2 Consortium
> Phone: +33 6 30 10 92 86
> im: jean.parpaillon at gmail.com
> skype: jean.parpaillon
> linkedin: http://www.linkedin.com/in/jeanparpaillon/en
> riak-users mailing list
> riak-users at lists.basho.com
More information about the riak-users