[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [openc2-lang] Versions in the Repository
So:
I have created a pull request for CS02 in the Master branch, but am unable to save it or name it. That's OK. We don't use the master in our normal work.
I have updated the Releases branch to WD15, that is the version we voted out as an Errata last November.
The Working Draft, where we should spend out time tomorrow, is verified to be at the WD15 level.
What this means is we can compare all the issues to the Working Branch to decide what issues we want to work in the LS. We will be discussing this tomorrow.
tc
From: duncan sfractal.com <duncan@sfractal.com>
Sent: Thursday, April 30, 2020 7:21 AM To: Considine, Toby <Toby.Considine@unc.edu>; openc2-lang@lists.oasis-open.org <openc2-lang@lists.oasis-open.org> Subject: Re: [openc2-lang] Versions in the Repository Works for me
Duncan Sparrell sFractal Consulting LLC iPhone, iTypo, iApologize I welcome VSRE emails. Learn more at http://vsre.info/
From:
openc2-lang <openc2-lang@lists.oasis-open.org> on behalf of Toby Considine <Toby.Considine@unc.edu>
The Releases Branch should have the latest version approved by TC and it does not
The Master branch should have approved Committee Specifications. I am not sure what is in there, but it is not the Committee Spec.
The Working Branch should follow work in flight.
I compared the Last Working Branch with the Committee Spec.
It appears to be correct - i.e. WD15 (errata) upon which the CS of November was based
My recommendation:
Fix Releases Branch and go forward (This means put current contents of Working into Releases) Fix Master Branch and go forward (Put current Committee Spec)
Use Working Branch to decide if Outstanding Issues are still Outstanding.
Is this OK with everyone?
tc |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]