Yup, I did notice the changes after we received the push into the CWE repository. It wasn't intentional. After a bit of digging, Mark found where the leakage occurred. Since the changes were items already in CWE-ou verbatim, we decided to go ahead and just accept the changesets as they appeared.
The topography of integrating back these Cyan changes to common merge points is what I expect I will use in the future (barring someone pointing out a major problem.) When something new comes in from Cyan, we'll apply those changes against the last revision CWE and CWE-ou have in common, and then merge those changes into the CWE-ou tip. Basically the same process anyone with a fork of CWE-ou will go through (on their side) if CWE-ou changes prior to the time the fork owner wants to integrate back.
I think this will give the most predictable behavior for others who wish to track the CWE-ou/CWE changes and have predictable reference changesets to work from.
_R
Proposed Open Source License update
Re: Proposed Open Source License update
One of the OpenUru toolsmiths... a bookbinder.
Re: Proposed Open Source License update
Many thanks to everyone involved in making this happen.