From: "Michael D Kinney via groups.io" <michael.d.kinney=intel.com@groups.io>
To: Rebecca Cran <rebecca@bsdio.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
Sean Brogan <spbrogan@outlook.com>,
"Oliver Smith-Denny" <osde@linux.microsoft.com>,
Pedro Falcato <pedro.falcato@gmail.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH edk2-CCodingStandardsSpecification v2 1/1] Prefer use of `static` C keyword over EDK2 type `STATIC`
Date: Mon, 3 Feb 2025 18:36:56 +0000 [thread overview]
Message-ID: <CO1PR11MB492926C18CF380A1BE90B571D2F52@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <dcedd919-d10b-4b9b-9755-632bc35ae13f@bsdio.com>
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 <rebecca@bsdio.com>
> Sent: Monday, February 3, 2025 10:29 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>;
> devel@edk2.groups.io; Sean Brogan <spbrogan@outlook.com>; Oliver
> Smith-Denny <osde@linux.microsoft.com>; Pedro Falcato
> <pedro.falcato@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/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2025-02-03 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 11:26 [edk2-devel] [PATCH edk2-CCodingStandardsSpecification v2 0/1] Prefer use of `static` C keyword over EDK2 type `STATIC` Rebecca Cran
2025-02-03 11:26 ` [edk2-devel] [PATCH edk2-CCodingStandardsSpecification v2 1/1] " Rebecca Cran
2025-02-03 18:17 ` Michael D Kinney via groups.io
2025-02-03 18:29 ` Rebecca Cran
2025-02-03 18:36 ` Michael D Kinney via groups.io [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CO1PR11MB492926C18CF380A1BE90B571D2F52@CO1PR11MB4929.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox