Hi Mike, Yes. the Revision history need to update. I have sent the spec patches v2 which update the Revision History in README.md and table of content in SUMMARY.md for INF/FDF/DSC spec. And I added the BZ in the README.md.
Thanks, Bob -----Original Message----- From: Kinney, Michael D Sent: Thursday, March 7, 2019 12:59 AM To: Gao, Liming <[email protected]>; Feng, Bob C <[email protected]>; [email protected]; Kinney, Michael D <[email protected]> Subject: EDK II Specifications for edk2-stable201903 tag Hi Liming and Bob, I see several EDK II specification updates. I do not see consistent updates to the Revision History In the README.md with link to the BZ for the document change. Please make sure all revision histories are up to date with BZ links, and as each BZ is closed put the links to commits made in the BZ. This allows anyone reading the documents to follow the link to the BZ from the Revision History, review the change request and follow the links to the commits in GitHub and the easily view the document changes. Do you want released versions of these documents to align with the edk2-stable201903 tag? The document release process is documented here: https://github.com/tianocore-docs/edk2-TemplateSpecification/wiki/TianoCore-Documents-Releasing If so, please enter BZ for each document with the requested release version number along with the SHA hash of on master the release branch is being requested. Thanks, Mike _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
