public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel@lists.01.org
Cc: Andrew Fish <afish@apple.com>,
	Brian Richardson <brian.richardson@intel.com>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Liming Gao <liming.gao@intel.com>,
	Michael Kinney <michael.d.kinney@intel.com>,
	Stephano Cetola <stephano.cetola@intel.com>
Subject: [edk2-wiki PATCH] release planning: announce the soft and hard feature freezes
Date: Thu,  8 Nov 2018 18:28:07 +0100	[thread overview]
Message-ID: <20181108172807.25233-1-lersek@redhat.com> (raw)

Add a paragraph to each of the SoftFeatureFreeze and HardFeatureFreeze
articles about the respective announcements on edk2-devel.

Cc: Andrew Fish <afish@apple.com>
Cc: Brian Richardson <brian.richardson@intel.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>
Cc: Stephano Cetola <stephano.cetola@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
---

Notes:
    Check out the rendered pages in my clone of the wiki:
    
    https://github.com/lersek/edk2/wiki/SoftFeatureFreeze
    https://github.com/lersek/edk2/wiki/HardFeatureFreeze

 HardFeatureFreeze.md | 8 ++++++++
 SoftFeatureFreeze.md | 8 ++++++++
 2 files changed, 16 insertions(+)

diff --git a/HardFeatureFreeze.md b/HardFeatureFreeze.md
index 01288dd03f71..e08f4c047e8d 100644
--- a/HardFeatureFreeze.md
+++ b/HardFeatureFreeze.md
@@ -4,3 +4,11 @@ tag](EDK-II#stable-tags).
 
 (This definition is modeled after QEMU's [hard feature
 freeze](https://wiki.qemu.org/Planning/HardFeatureFreeze)).
+
+# Announcing the hard feature freeze
+
+The proposed schedule for the active development cycle is shown in the [EDK II
+Release Planning](EDK-II-Release-Planning) article. Shortly before the hard
+feature freeze, an announcement email is sent to the
+[edk2-devel](https://lists.01.org/mailman/listinfo/edk2-devel) mailing list; by
+default by [Liming Gao](https://github.com/lgao4/).
diff --git a/SoftFeatureFreeze.md b/SoftFeatureFreeze.md
index 9dc7d9c19369..e33dd80ccbee 100644
--- a/SoftFeatureFreeze.md
+++ b/SoftFeatureFreeze.md
@@ -40,3 +40,11 @@ communicate with the maintainer about their intentions. It also helps if you:
 
 (This definition is modeled after QEMU's [soft feature
 freeze](https://wiki.qemu.org/Planning/SoftFeatureFreeze).)
+
+# Announcing the soft feature freeze
+
+The proposed schedule for the active development cycle is shown in the [EDK II
+Release Planning](EDK-II-Release-Planning) article. Shortly before the soft
+feature freeze, an announcement email is sent to the
+[edk2-devel](https://lists.01.org/mailman/listinfo/edk2-devel) mailing list; by
+default by [Liming Gao](https://github.com/lgao4/).
-- 
2.19.1.3.g30247aa5d201



             reply	other threads:[~2018-11-08 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 17:28 Laszlo Ersek [this message]
2018-11-09 10:05 ` [edk2-wiki PATCH] release planning: announce the soft and hard feature freezes Leif Lindholm
2018-11-09 15:09   ` Gao, Liming
2018-11-09 16:26     ` Laszlo Ersek
2018-11-09 17:07       ` Kinney, Michael D
2018-11-09 17:18         ` Laszlo Ersek
2018-11-10 14:20           ` Gao, Liming

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=20181108172807.25233-1-lersek@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