[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Some reminders about Helios M4
|
> What do we need to do to express intent ...
In case others are waiting the answer ... there's a field in the portal
meta data for each project call 'simultaneiousrelease' that can be edited
to "helios=1'.
But looks like you (or someone) figured that out for buckminster (or,
maybe the database/script has some delay?) But in either case, the list is
growing! Soon, we'll
start discussing how to organize it.
dsdp.mtj
dsdp.tml
dsdp.tml
eclipse
eclipse.jdt
eclipse.pde
eclipse.platform
modeling.amalgam
modeling.emf
modeling.emf.compare
modeling.emf.eef
modeling.emf.teneo
modeling.emf.teneo
modeling.emf.teneo
modeling.emft.mint
modeling.emft.mwe
modeling.m2m.atl
modeling.m2t
modeling.m2t.acceleo
modeling.m2t.jet
modeling.m2t.xpand
modeling.mdt.ocl
modeling.mdt.uml2
modeling.mdt.xsd
modeling.tmf.xtext
rt.ecf
rt.eclipselink
rt.equinox
rt.jetty
rt.rap
rt.swordfish
stp.sca
technology.egit
technology.jwt
technology.mat
technology.packaging
technology.subversive
tools.buckminster
tools.cdt
tools.gef
tools.mylyn
tools.ptp
tptp
webtools
webtools.dali
From:
Thomas Hallgren <thomas@xxxxxxx>
To:
cross-project-issues-dev@xxxxxxxxxxx
Date:
12/14/2009 09:21 AM
Subject:
Re: [cross-project-issues-dev] Some reminders about Helios M4
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
Hi Dave,
What do we need to do to express intent for Buckminster? I thought we had
done that already.
Regards,
Thomas Hallgren
On 2009-12-14 14:32, David M Williams wrote:
No, this is a list of those that _have_ expressed intent ... I'm sending a
positive list for once! And I clearly see "technology.subversive" in this
list, so I think you are all set. (Let me know if I'm misunderstanding).
And, the list has grown quite a bit in just a day or two. Here's the ones
I see "marked" now. No idea why "dsdp.tml" is listed twice (this list is
based on a little PHP script) but I'll leave it in the list twice, in case
its a sign of a database problem of some sort (more likely a script bug?
we can sort out later).
dsdp.tml
dsdp.tml
eclipse
eclipse.jdt
eclipse.pde
eclipse.platform
modeling.amalgam
modeling.emf.compare
modeling.emf.eef
modeling.emft.mwe
modeling.m2m.atl
modeling.m2t
modeling.m2t.acceleo
modeling.m2t.xpand
modeling.mdt.ocl
modeling.mdt.uml2
modeling.tmf.xtext
rt.ecf
rt.eclipselink
rt.equinox
rt.jetty
rt.rap
rt.swordfish
stp.sca
technology.egit
technology.jwt
technology.mat
technology.packaging
technology.subversive
tools.gef
tools.mylyn
tools.ptp
webtools
webtools.dali
From:
"Igor V. Burilo" <igor.burilo@xxxxxxxxxxxx>
To:
"'Cross project issues'" <cross-project-issues-dev@xxxxxxxxxxx>
Date:
12/14/2009 03:32 AM
Subject:
RE: [cross-project-issues-dev] Some reminders about Helios M4
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
Hello David,
Subversive project is listed in projects list which didn't express intent
for Helios, but I marked simultaneousrelease flag about week ago; I
checked it once again and it's really set.
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [
mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M
Williams
Sent: Friday, December 11, 2009 8:01 PM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: [cross-project-issues-dev] Some reminders about Helios M4
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
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
