Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-ocl.dev] Re: MDT OCL Project Plan for Helios (take 2)
Hi All

I've gone through all the open Bugzillas. After closing a couple and opening a couple we now have only 91 bugs! Very tractable.

The attached spreadsheet gives my analysis. Columns A-L from Bugzilla.
-----------------------
Column M; what I think we should do. 14 to Defer possibly till after Helios.
Column N; what I think could be a plan theme (not introducing any new themes).

I don't really mind which bugs appear in the plan. I'm not that keen to inflict 77 bugs on the plan, so I've refrained from
re-annotating each bug. I'm happy just to set a Helios milestone on the 77 and --- on the other 14. However if we plan to
do 77 perhaps we should put them all in.

How many of these do we want in the plan?

I don't intend to change Kenn's plan without further discussion.
-----------------------
Column O; the relevant sub-components.

Some of these like ui and tests could be keywords. Could the others?
Perhaps they could be Whiteboard, but with no obvious definition of Whiteboard, I don't know what tools will get confused.
I think that the Column O names can be transferred to tags, so that you can just search on 'library' and get all the library bugs.

 A note on some of the less obvious components:

ast - requires a change to OCL:.ecore/OCL.uml and associated code
console - the old interpreter example
environment - the shared heart of the analyzer/validator/evaluator support
future - brand new functionality
internationalization - some annoying hand-me-downs
language - areas awaiting design and associated OMG issues

I regard myself as mainly involved in/responsible for analyzer, ast, editor, language, parser, registry, ui with some shared involvement in environment, tests and one day synthesis.

Any volunteers for the other sub-components.

Is use of tags for the sub-components a good idea?

If the team is happy, I'll tag every bug as per Column O and change the targets to Helios on Wednesday.

    Regards

       Ed Willink





Kenn Hussey wrote:
The rolled-up plan won't pick up additions/changes to themes (i.e. the whiteboard field in Bugzilla) automatically, but if you let me know once the OCL plan has been updated accordingly, I'll go ahead and make the necessary changes to the MDT plan.

Thanks,

Kenn

On Fri, Sep 25, 2009 at 12:10 PM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
Hi Kenn

I'm hoping to find time on Sunday to go through every Open OCL Bugzilla and keyword it to a theme and sub-theme or defer it according to what I think we should do for Helios.

This will be before 30th.

Will your tooling pick this up automatically or will it cause chaos?

    Regards

       Ed Willink


Kenn Hussey wrote:
Thanks Alex. You might want to change the name of the final milestone from "1.4.0" to "Helios", and it would be nice(r) if the compliance items could have a whiteboard of "Compliance" rather than "OCL 2.1", but everything else looks great! I've updated the rolled-up MDT plan to take your changes into account - see http://www.eclipse.org/projects/project-plan.php?projectid=modeling.mdt.

Cheers,

Kenn

On Thu, Sep 24, 2009 at 8:48 AM, Alexander Igdalov <alexander.igdalov@xxxxxxxxx> wrote:
Hi all,
 
Please take a look on the second version of the plan.
 
 
Kenn, Ed, thanks for your comments.
 
Cheers,
- Alex.


_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev


_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev



_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev

Attachment: bugs-2009-09-25.xls
Description: MS-Excel spreadsheet

Back to the top