Release process is documented here
https://github.com/tianocore-docs/edk2-TemplateSpecification/wiki/TianoCore-Documents-Releasing
The "version" field in the main branch is ignored, so there is never any reason
to change it.
That field typically contains the value when the document was imported into
GitHub.
Version 2.3 was not missed. It is set to that value in the release branch for
2.3.
https://github.com/tianocore-docs/edk2-CCodingStandardsSpecification/tree/release/2.30
Change made in a commit on that release branch:
https://github.com/tianocore-docs/edk2-CCodingStandardsSpecification/commit/d4735e4d57c8336c19c94fc33367a2b41c0193ff
The change history in Readme.MD are correct.
Mike
> -----Original Message-----
> From: Rebecca Cran <rebe...@bsdio.com>
> Sent: Monday, February 3, 2025 10:29 AM
> To: Kinney, Michael D <michael.d.kin...@intel.com>;
> devel@edk2.groups.io; Sean Brogan <spbro...@outlook.com>; Oliver
> Smith-Denny <o...@linux.microsoft.com>; Pedro Falcato
> <pedro.falc...@gmail.com>
> Subject: Re: [PATCH edk2-CCodingStandardsSpecification v2 1/1] Prefer
> use of `static` C keyword over EDK2 type `STATIC`
>
> On 2/3/25 11:17 AM, Kinney, Michael D wrote:
> > Version is ignored when "draft" is "yes", so this change can be
> dropped.
> >
> > book.json should only be updated in a release branch to publish a
> new release.
>
>
> Do we have a process to make sure book.json is updated? It looks like
> version 2.3 was missed.
>
> Also, should I keep the change mentioning version 2.4 in README.md? Or
> will that be updated in the release branch too?
>
> I'll send out a v3 soon.
>
> --
>
> Rebecca
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121073): https://edk2.groups.io/g/devel/message/121073
Mute This Topic: https://groups.io/mt/110968939/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
