[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[emft-dev] Re: [emf-dev] What happened to bugzilla's Target Milestones?
|
I asked for the x.yMz and x.yRCz milestones to be purged, as well as the Mz and RCz ones for EMFT (so I could reorder them).
Sorry for the extra administrivia.
Frankly, I'm not sure that the Galileo-EMO-bugs being assigned to a specific milestone provides much more information than "Past". Either way they're already done, right? Does anyone beyond the EMO or the PMC care when they were targetted? Isn't the close date more useful anyway?
Nick
On Mon, Nov 24, 2008 at 9:27 AM, Christian W. Damus
<cdamus@xxxxxxxxxxxxx> wrote:
Hi, Ed,
Yes, those generic milestone targets do still appear, but they seem to have been re-created from scratch or something, because any bug that was targeted against them now is targeted to "Past."
Remember the hour I spent assigning those milestones one-by-one to all of the EMO-raised Galileo requirements in EMF and EMFT? All undone.
cW
On 24-Nov-08, at 9:22 AM, Ed Merks wrote:
I though we were cleaning up things like 1.1M1 1.1M2 but not generic M1 and M2 which we need for the project planning.. Those things do appear in the drop down for me. I thought everyone had agreed to use that approach. Am I not understanding something?
Christian W. Damus wrote:
Hi, Nick,
All of my in-plan bugs were tagged with the generic M4, M5, etc. milestones. That information must now be recovered (manually, by me) as all of these bugs are now targeted for "Past".
Also, it is conventional across all Eclipse projects to target in-plan committed enhancements against specific milestones. This is not a matter of opinion. The convention also includes using the release number as a target milestone to indicate "proposed for this release but not definitely planned into a milestone." Should I use the "Galileo" target for this purpose, now?
It would have been nice to discuss a change of this kind of cross-component scope on the mailing list before it happened, so that we could assess the impact.
Cheers,
Christian
On 23-Nov-08, at 12:28 AM, Nick Boldt wrote:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=255467
https://bugs.eclipse.org/bugs/show_bug.cgi?id=255468
IMHO, your queries shouldn't include milestones. The milestone value will appear in the rendered HTML, crossed out once complete. So you can query for all bugs with the Galileo+ keyword, and the plan doc will show when they're slated (ie., what milestone).
http://wiki.eclipse.org/Development_Resources/Project_Plan/Modeling_Project
Nick
Eike Stepper wrote:
Hi,
I noticed that bugzilla now only offers "Past" and Future" as possible values for the Target Milestone. Could somebody explain the rationale behind this?
It seems that *all* my existing bugzillas have been crippled with these values, thereby completely destroying my carefully setup bugzilla queries for the project plan ;-(
Did I miss any action point??
Cheers
/Eike
----
http://thegordian.blogspot.com
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev
--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
Release Engineer :: Eclipse Modeling & Dash CBI
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev
--
Christian W. Damus
Senior Software Developer, Zeligsoft Inc.
Component Lead, Eclipse MDT OCL and EMF-QTV
E-mail: cdamus@xxxxxxxxxxxxx
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev
--
Nick Boldt :: JBoss, a division of Red Hat
Productization Lead :: JBoss Tools & Dev Studio
Release Engineer :: Eclipse Modeling & Dash CBI
http://wiki.eclipse.org/User:Nickb
