[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[mdt-ocl.dev] RE: [mdt.dev] Some reminders about Helios M4
|
Hi All,
I am very sorry for having confused the dates. I am starting
to build OCL 3.0.0 M4 right away.
Sorry for the inconvenience,
- Alex.
Alex,
Please respond.
Thanks,
Kenn
---------- Forwarded message ----------
From:
Anthony Hunter <anthonyh@xxxxxxxxxx>Date:
Tue, Dec 15, 2009 at 5:41 PM
Subject: Re: [mdt.dev] Some reminders about
Helios M4
To: MDT developers <
mdt.dev@xxxxxxxxxxx>
Hi Team,
Are we going to publish an OCL 3.0.0
M4?
Cheers...
Anthony
--
Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software Development
Manager
IBM Rational Software: Aurora / Modeling Tools
Phone:
613-270-4613
Kenn
Hussey ---2009/12/13 10:53:36 PM---Team, Please see the email below, in
particular #2. If your project is planning to participate in the Helios release
train, you
Team,Please
see the email below, in particular #2. If your project is planning to
participate in the Helios release train, you must declare this by updating the
metadata for your project in the Portal. Please see http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php for the requirements that your project must meet in order to be on the
train.Cheers,Kenn---------- Forwarded message
----------
From: David M Williams <david_williams@xxxxxxxxxx>
Date: Fri,
Dec 11, 2009 at 12:45 PM
Subject: [cross-project-issues-dev] Some reminders
about Helios M4
To: cross-project-issues-dev@xxxxxxxxxxx
1. its next Friday, 12/18!
2. That's the deadline for expressing intent to participate in
Helios, which is formally done by marking the simultaneousrelease flag in
Eclipse Portal (there's a Helios field to edit to "1"). The list is
currently (understandably) short, so I'll keep my eye on it, and send more nag
notes if expected teams don't mark soon.
modeling.amalgam
modeling.emf.compare
modeling.emf.eef
modeling.m2t.acceleo
rt.jetty
rt.swordfish
stp.sca
technology.egit
technology.subversive
tools.ptp
webtools
3. I suggest we not "announce" our individual Project
milestones until the Helios M4 date, 12/18. Of course, we need to announce on
mailing lists, etc., for our committers and adopters ... I just mean the general
news items, forums, and similar, targeted to general end-users asking for early
testing. That is what we have to do for the final release, and I suggest
we get in the habit of working "simultaneously" now, even during milestones. Not
a huge problem, but I do recall some issue in the past where there were
complaints or questions, because someone tried to update part of their
environment, but couldn't, since some other part had not release an M4 version
yet. Ends up being frustrating and making us appear unorganized. (And we all
know that's not true :)
Thanks,
_______________________________________________
cross-project-issues-dev
mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
mdt.dev
mailing list
mdt.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt.dev
_______________________________________________
mdt.dev
mailing list
mdt.dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/mdt.dev