Re: Proposal: OpenMAMA Default Branch change to "next"
Sounds quite sensible to me, Frank.
Nigel Phelan | Corporate & Investment Bank | Market Data Services | J.P. Morgan
From: Openmama-dev@... [mailto:Openmama-dev@...] On Behalf Of Frank Quinn
Sent: 25 August 2020 12:35
Subject: [Openmama-dev] Proposal: OpenMAMA Default Branch change to "next"
I would like to propose that we change the OpenMAMA github default git branch to “next” instead of “master”.
This would mean that:
Note all existing clones etc would remain unchanged so this won’t actually “break” anything for existing OpenMAMA developers.
The rationale being that “master” is reflective of the last stable release, but it’s also the source of the main README output when visitors come to the github page which makes it look like the project is less active than it actually is, repo documentation effectively slows down to match the biannual release cycle etc.
The industry in general is also gradually moving away from the “master” nomenclature for branches with linux and github both making noises about moving away from defaulting to that branch name, so this would pave the way for eventual retirement of the branch name (which is actually fine - we can just use our release branches instead as we already do with minimal impact).
If anyone has any comments or feedback on this, please respond on this thread.
T: +44 (0) 28 8678 8015
This message is confidential and subject to terms at: https://www.jpmorgan.com/emaildisclaimer including on confidential, privileged or legal entity information, malicious content and monitoring of electronic messages. If you are not the intended recipient, please delete this message and notify the sender immediately. Any unauthorized use is strictly prohibited.