[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-ui-dev] Identifying backport candidate
|
I usually prefer to have only one bug report
for a fix. General rule is that a bug is fixed in all versions equal and
higher than indicated in the target milestone.DaniFrom:
Mickael Istria <mistria@xxxxxxxxxx>To:
"Eclipse Platform
UI component developers list." <platform-ui-dev@xxxxxxxxxxx>Date:
27.06.2016 10:19Subject:
[platform-ui-dev]
Identifying backport candidateSent by:
platform-ui-dev-bounces@xxxxxxxxxxx
Hi all,I'd like to "annotate" of few bugzilla entries
as candidate for backport as they meet the criteria detailed earlier on
this mailing-list, except that the patch is not yet "mature":
it's been merged to master recently and has been reviewed as safe enough,
but it requires some real-life testing before being considered for backport.
What is the best way to track that before sending request
to PMC. Is it better to create a new entry with a different target version,
or to just add a tag or keyword on the bug? If the later, is there one
already existing?
Thanks in advance,
--
Mickael Istria
Eclipse developer at JBoss,
by Red Hat
My
blog - My
Tweets_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev