Mike: It is OK to me. I have no other comments. Thanks Liming

I'd suggest just using the Gitlab mirror. Unlike cryptomilk.org, Gitlab should be just as reliable as Github and won't introduce another potential failure point. -- Rebecca Cran

I like it. - Bret Sent: Saturday, December 19, 2020 10:59 AM To: rfc@edk2.groups.io<mailto:rfc@edk2.groups.io>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Bret

Hello, There have been a few suggestions to create a mirror of cmocka in TianoCore org in GitHub. I have found a GitHub action that can do a repo sync.

Hello, The following bug has been fixed on edk2/master https://bugzilla.tianocore.org/show_bug.cgi?id=3111 https://github.com/tianocore/edk2/pull/1226 This bug is also considered a

I agree that the default policy is to only support a branch until the next stable tag. My comments were only to address the potential for a request after that defined support timeline. If a portion

Mike: This case is clear. One commit is for the bug fix, another is for the unit test. If the unit test is also important for this fix, it can be cherry-pick. I understand the critical bug fix is

Mike: I review all submodules in edk2. They are all from github except for cmocka. So, I agree to use github mirror for cmocka. Thanks Liming

Mike: [Liming] This one is for unit test. It is not critical fix. I don't think it is required. Here is my suggestion on the live period of the stable tag branch. The stable tag branch will be

“I agree with Liming that stable branches should have a predefined lifetime. Keeping stable branches regression-free is very difficult and ungrateful work, and the community should not have

My vote is to own a fork. I agree with Laszlo that it’s very low maintenance (may even be able to automate it with an existing DevOps pipeline to run every day) and gives us the most control of our

Also, apparently Neverware is part of Google: https://cloudreadykb.neverware.com/s/article/Neverware-is-now-part-of-Google-FAQ -- Rebecca Cran

I'm sorry, this was silly. The whole point of git is "addressing by content". Our submodule reference in edk2 makes us check out the cmocka tree at a known hash, so where that comes from is totally

We could create our own fork under the <https://github.com/tianocore> organization. It does not require much extra maintenance or monitoring, in my opinion. We only need to advance our fork to the

- Looks good; just a typo in the example: "edk2-stable201111.01" should use 2020, not 2011. - I agree with Liming that stable branches should have a predefined lifetime. Keeping stable branches

Sounds good to me as well, thanks! Laszlo

Hello, We have had at least three incidents in the last year where the link to the cmocka submodule in the UnitTestFrameworkPkg has not been available, and this impacted the EDK II CI system. The

Hello, The following bug has been fixed on edk2/master https://bugzilla.tianocore.org/show_bug.cgi?id=3111 https://github.com/tianocore/edk2/pull/1226 This bug is also considered a critical

Hi Leif, Thank you for the feedback. I will send a revised RFC soon. I will discuss with Liming in the Tianocore bug scrub this evening. Mike