From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, michael.d.kinney@intel.com
Subject: Re: [edk2-devel] Need newer releases/tags added to TianoCore Bugzilla
Date: Thu, 2 Apr 2020 13:53:20 -0600 [thread overview]
Message-ID: <dd157179-e69d-3cca-024a-c11d942f82dd@bsdio.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9EF38FE@ORSMSX113.amr.corp.intel.com>
Okay, but the edk2-stable202002 release is also missing.
--
Rebecca Cran
On 4/2/20 1:24 PM, Michael D Kinney wrote:
> Rebecca,
>
> The current use of that field is to identify previous
> releases that a bug fix needs to be propagated to.
>
> We do not know the exact release name for future releases
> until we make the release.
>
> I recommend you use the "Deadline" field to provide
> the date the feature must be implemented, reviewed,
> and committed in order to make the release that is
> targeted.
>
> In many cases the set of work items for a specific
> target release need to have deadlines well before
> the soft/hard freeze dates and will not have the
> same deadline date. Only providing the target release
> name is not enough to properly plan tasks.
>
> Thanks,
>
> Mike
>
>> -----Original Message-----
>> From: devel@edk2.groups.io <devel@edk2.groups.io> On
>> Behalf Of Rebecca Cran
>> Sent: Thursday, April 2, 2020 11:52 AM
>> To: Kinney, Michael D <michael.d.kinney@intel.com>;
>> devel@edk2.groups.io
>> Subject: [edk2-devel] Need newer releases/tags added to
>> TianoCore Bugzilla
>>
>> At least for the Feature Requests, the "Release(s) the
>> issue is
>> observed" and "Release(s) the issues must be fixed"
>> fields are outdated,
>> and missing newer tags.
>>
>> I haven't checked if the other areas such as bug reports
>> also need updated.
>>
>>
>> --
>>
>> Rebecca Cran
>>
>>
>>
>>
>
>
>
next prev parent reply other threads:[~2020-04-02 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 18:52 Need newer releases/tags added to TianoCore Bugzilla Rebecca Cran
2020-04-02 19:24 ` [edk2-devel] " Michael D Kinney
2020-04-02 19:53 ` Rebecca Cran [this message]
2020-04-02 20:07 ` Michael D Kinney
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=dd157179-e69d-3cca-024a-c11d942f82dd@bsdio.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