public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>
Cc: "Liming Gao (Byosoft address)" <gaoliming@byosoft.com.cn>
Subject: [edk2-devel] EDK II Release Planning: update content for edk2-stable202311
Date: Fri, 27 Oct 2023 00:31:00 +0200	[thread overview]
Message-ID: <13ccb295-4ffd-e881-782e-e5ca59f60376@redhat.com> (raw)

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning#edk2-stable202311-tag-planning

I've scanned the edk2 git commit range edk2-stable202308..f945b72331d7,
and collected (and when necessary, closed/updated) TianoCore BZs. When
TianoCore BZs were not available, I tried capturing other bug tracker
references, or at least those (larger) mailing list patch sets that had
been merged.

Wiki commit 0ea77aeccca8.

If anyone is missing a feature or bugfix they'd like to see on the list,
please go ahead and update the wiki, or (if you don't have permission?)
comment in this thread.

There is still more than a week until the Soft Feature Freeze, so it
would be nice to update the planning page immediately whenever a feature
or an important bugfix is merged. The QEMU project policy is generally
that, whenever a pull request is merged, important changes are
immediately documented by the maintainer on the upcoming release's
Planning wiki page. That tends to work much better than retroactively
collecting tickets (... because in many cases we don't even file
tickets) or scraping the commit history (... because the commit history
is long, and doesn't capture cover letters).

Laszlo



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#110143): https://edk2.groups.io/g/devel/message/110143
Mute This Topic: https://groups.io/mt/102210493/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



                 reply	other threads:[~2023-10-26 22:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=13ccb295-4ffd-e881-782e-e5ca59f60376@redhat.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