public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Wang, Fan" <fan.wang@intel.com>
Subject: Re: [edk2-devel] [Patch] Updated EDK II Release Notes
Date: Tue, 30 Apr 2019 03:31:00 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E43FC0C@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1d73cd15-d18a-52f7-6287-1f7f2cc7732f@redhat.com>

> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Tuesday, April 30, 2019 2:51 AM
> To: devel@edk2.groups.io; Wang, Fan <fan.wang@intel.com>
> Cc: Gao, Liming <liming.gao@intel.com>
> Subject: Re: [edk2-devel] [Patch] Updated EDK II Release Notes
> 
> On 04/28/19 04:22, Wang Fan wrote:
> > Remove IpSec driver and IpSecConfig application in NetworkPkg for BZ1697.
> >
> > Cc: Liming Gao <liming.gao@intel.com>
> > Signed-off-by: Wang Fan <fan.wang@intel.com>
> > ---
> >  EDK-II-Release-Notes.md | 5 +++++
> >  1 file changed, 5 insertions(+)
> >
> > diff --git a/EDK-II-Release-Notes.md b/EDK-II-Release-Notes.md
> > index 892ceaf..e080082 100644
> > --- a/EDK-II-Release-Notes.md
> > +++ b/EDK-II-Release-Notes.md
> > @@ -43,5 +43,10 @@ Platform FDF also needs to be changed to include DebugServicePei and place it in
> >  APRIORI PEI {
> >    INF  MdeModulePkg/Universal/DebugServicePei/DebugServicePei.inf
> >    }
> >  INF  MdeModulePkg/Universal/DebugServicePei/DebugServicePei.inf
> >  ```
> > +
> > +2. Remove IpSec driver in NetworkPkg for BZ1697, also include IpSecConfig application. Below components should be removed from
> platform DSC/FDF files:
> > +
> > +NetworkPkg/Application/IpsecConfig/IpSecConfig.inf
> > +NetworkPkg/IpSecDxe/IpSecDxe.inf
> >
> 
> I'm confused. I thought we were tracking the release notes for the upcoming stable release at:
> 
>   https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning
> 
> and that we only tracked release notes for past releases at
> 
>   https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Notes
> 
EDK-II-Release-Notes is added to track this release note. Past release notes are in edk2 GitHub release tag. 

> with the idea that, once a tag is made / released, we move the content from "release planning" to "release notes".
> 
Once the tag is made, EDK-II-Release-Notes will be moved into edk2 GitHub release tag. It will be clear for next release. 

> If we modify both wiki articles in parallel, then it's easy to lose synch between them, for the currently in-progess stable release.
> 
Release Notes keep Wiki and Update Notes. The feature planning are in EDK-II-Release-Planning. 
To reduce the confuse, I will remove the feature planning from EDK-II-Release-Notes wiki.

> Personally I'd like to add <https://bugzilla.tianocore.org/show_bug.cgi?id=1747> to the "release planning" article soon, but now this
> change confuses me.
> 
Still add this feature into EDK-II-Release-Planning.

> Thanks
> Laszlo

      reply	other threads:[~2019-04-30  3:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28  2:22 [Patch] Updated EDK II Release Notes Wang Fan
2019-04-28  8:26 ` Liming Gao
2019-04-29 18:51 ` [edk2-devel] " Laszlo Ersek
2019-04-30  3:31   ` Liming Gao [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E43FC0C@SHSMSX104.ccr.corp.intel.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