| Re: [eclipse-pmc] What to do with deferred plan items |
I also feel that the plan keyword captures something we shouldn't lose
track of.
To be committed, a plan item needs a target milestone. So I think, deferred
plan items should simply be decommitted by removing their target.
Sidenote: There are quite a few bugs with '[plan item]' or '[plan]' prefix
in summary which are not carrying a 'plan' keyword.
John Arthorne
<John_Arthorne@ca
.ibm.com> To
Sent by: eclipse-pmc@xxxxxxxxxxx
eclipse-pmc-bounc cc
es@xxxxxxxxxxx
Subject
Re: [eclipse-pmc] What to do with
05/16/2007 09:29 deferred plan items
PM
Please respond to
eclipse-pmc@eclip
se.org
I would suggest leaving the keyword for now. It may be useful information
when gathering inputs for the next plan. In the past the plan keyword has
been removed from old bugs immediately prior to creating the new plan item
bugs when the new plan becomes available.
Chris Goldthorpe
<cgold@xxxxxxxxxx>
Sent by: To
eclipse-pmc-bounces@xxxxxxxxxx eclipse-pmc@xxxxxxxxxxx
g cc
Subject
16/05/2007 03:07 PM [eclipse-pmc] What to do with
deferred plan items
Please respond to
eclipse-pmc@xxxxxxxxxxx
I have a procedural question about deferred plan items. What should we do
with the bug reports? Presumably we would want to remove the target
milestone of 3.3, do we also want to remove the keyword "plan".
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc