Re: [mdt.dev] Plans for Indigo

[ed@xxxxxxxxxxxxxxxxxx]

Hi Anthony, Kenn

The OCL plan is a working draft, awaiting the PMC wake up call to finish
it off.

Rest assured there will NOT be an OCL 4.0.0 for Indigo.

My current plans are to do the major development in MDT/OCL Examples,
and promote to non-examples immediately after Indigo so that there is a
full year to resolve ripples.

There will be an MDT/OCL 4.0.0 for Indigo+1.

The Indigo release will be 3.1 or 3.2 depending on whether we need an
interim release to freeze enhanced functionality after UML/EMF/Xtext break
Helios compatibility. I would like OCL 3.1Mx to remain a viable Helios
add-in for as long as possible.

[Most of the MDT/OCL 3.0.0 compatibility was actually a failure to move
away from emf.ocl a couple of years earlier.]

	Regards

		Ed Willink
>
> Hi Kenn,
>
> Thanks for the plans. I happened to notice that OCL stated a target
> milestone of 4.0.0. Are we really going to do a major release of OCL two
> years in a row? A bunch of the modeling projects and third party
> applications will be broken once again by moving to 4.0.0. We did UML2
> 3.0.0 in Ganymede and OCL 3.0.0 in Helios. This at minimum required
> everyone to update plug-in version tolerance in their bundles, which while
> supposedly trivial, still involves a significant amount of work given the
> number of bundles involved. It took my application team three weeks to
> access the last set of OCL API changes and adopt OCL 3.0.0.
>
> Can we reconsider doing a major release of any component in Indigo?
>
> I will have to think about what I want to do about EMF Transaction, EMF
> Validation and EMF Query, all of which have either a code or build
> dependency on OCL.
>
> Cheers...
> Anthony
> --
> Anthony Hunter mailto:anthonyh@xxxxxxxxxx
> Software Development Manager
> IBM Rational Software: Aurora / Modeling Tools
> Phone: 613-270-4613
>
>
>
>
> From:       Kenn Hussey <kenn.hussey@xxxxxxxxx>
> To:         Eclipse MDT Developers <mdt.dev@xxxxxxxxxxx>
> Date:       10/05/2010 09:42 PM
> Subject:    [mdt.dev] Plans for Indigo
> Sent by:    mdt.dev-bounces@xxxxxxxxxxx.
>
>
>
> Team,
>
> Sorry for being late with this (project plans are typically due by the end
> of September), but I have finally put a "rolled-up" plan in place for the
> upcoming Indigo release of MDT, accessible at
> http://www.eclipse.org/projects/project-plan.php?projectid=modeling.mdt..
> Project leads, please let me know as soon as your Indigo plans are ready
> so
> that they can be included in the overall MDT plan (so far, only OCL and
> UML2 are in place). Alternatively, if you're not planning a release, you
> may want to consider scheduling a termination review for your project
> (e.g., SBVR, IMM, MST, UML2 Tools?).
>
> As a reminder, your plan should be located in the 'project-info' folder of
> your project's Web space in CVS. Ideally, you would have two files there -
> a plan.xml file (or soft link) which always holds the content of your
> current plan (and which is referenced from the portal), and a
> plan_<release>.xml file which holds the content for a specific release.
> This is useful so that, in the future, it's still possible to go back and
> look at the plan for a particular release.
>
> If you're not sure how to structure the contents of your plans, please
> take
> a look at the ones for OCL and UML2 as examples. Of course, don't hesitate
> to contact me if I can help in any way...
>
> Thanks,
>
> Kenn
> _______________________________________________
> mdt.dev mailing list
> mdt.dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mdt.dev
> _______________________________________________
> mdt.dev mailing list
> mdt.dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mdt.dev
>