AMP is no longer a concern. We're going to keep with our minimal placeholder site for M6 -- not worth risk to try to get it in now. On top of other issues, I've just discovered a broken API dependency on MWE 1.1 that I should have discovered at M5 but missed as we were still dealing with git/build issues at that point.. (AMP users should not use features from the Indigo update site but from our forthcoming milestone site.)
David, et.al..
It's ok if we add features to M7 or do we have to try to get an exception for that?
cheers,
Miles
On Mar 16, 2011, at 11:59 AM, David M Williams wrote: > *I'd actually prefer to put those
dependencies into the GEF3D build
> itself, but I'm not sure what the policy is WRT to projects building
> dependencies on non-train Eclipse projects to support their own
> dependencies. Ny guidance on that
would be much appreciated.
The policy is "no". Anything
in the Eclipse common repository can only depend on other things in the
Eclipse common repository. I could not find where that was written
down, but my memory is that we once tried, and it just sounded confusing
and everyone thought it pretty clearly implied by "simultaneous release".
HTH
From:
Miles Parker <milesparker@xxxxxxxxx>
To:
Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>
Cc:
AMP developer mailing
list <amp-dev@xxxxxxxxxxx>
Date:
03/16/2011 02:28 PM
Subject:
Re: [cross-project-issues-dev]
Status and outlook for Indigo M6 on +3
day
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
Hi David,
AMP may be a weak link here. It's a complicated story
but the upshot is bad timing having only tangentially to do with train
dependencies and more to do with triage. 1) We've been trying to resolve
some IP issues and factor stuff out and reorganize the build components
for our dependencies on GEF3D for that (I'm trying to put together a build
for GEF3D to support but we'll probably continue to host and maintain that
w/in AMP*) with our minimal set of current features. 2) this am we've had
a submission for some key/major functionality from new contributors --
as we're supposed to be at API freeze for M6 and I'd like to have this
available for EclipseCon I'm going to make a try at getting this all in.
This doesn't introduce any new dependency issues, it just has to do with
having the aggregator match the feature set of what's in the update site.
Anyway, I had been worrying that this might push past COB into the evening,
and I'm at PST here. In any case we will *not* push past today, and we'll
just disable and go back to minimal set should this impact anyone's pre-EclipseCon
stress level.
thanks,
Miles
*I'd actually prefer to put those dependencies into the
GEF3D build itself, but I'm not sure what the policy is WRT to projects
building dependencies on non-train Eclipse projects to support their own
dependencies. Ny guidance on that would be much appreciated.
On Mar 16, 2011, at 9:39 AM, David M Williams wrote:
Busy week? Already headed to EclipseCon?
:)
Thanks Nicolas, for keeping us all informed.
Which reminded me ... today is +3 day, all contributions should be complete
today and EPP packages generated by Thursday morning ... the following
are all the contribution files that (still) contain enabled="false"
for the contribution or a feature.
Is this list as expected? Anyone forget to re-enable? Should any
of these contribution files (or features) be removed? (That is, not in
Indigo after all ... and just mistakenly left in?)
gmp-gmf-runtime.b3aggrcon
gmp-gmf-tooling.b3aggrcon
gyrex.b3aggrcon
mdt-modisco.b3aggrcon
mdt-papyrus.b3aggrcon
We will be looking to lock down the M6 repository early, since many will
be traveling Friday/Saturday/Sunday for EclipseCon ... so, 1) please try
to finish early, and 2) be sure to keep us informed if anyone will be late
... especially later than "end of day" today ... let's say that's
5 PM Eastern. We can restart a build, say, at 6 or 7 ... if needed ...
but after that we'll start to impact our stress free schedule.
Thanks everyone,
From: Nicolas
Bros <nbros@xxxxxxxxxxxxxxxx>
To: cross-project-issues-dev
<cross-project-issues-dev@xxxxxxxxxxx>
Date: 03/16/2011
12:04 PM
Subject: [cross-project-issues-dev]
MoDisco late contribution
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Hi,
The last MoDisco contribution made the aggregator fail so I disabled it.
I'll try to fix the problem and re-enable it again once it's solved.
--
Nicolas Bros
R&D
tel: 06 75 09 19 88
nbros@xxxxxxxxxxxxxxxx
nbros.mia@xxxxxxxxx
Mia-Software, 410 clos de la Courtine
93160 Noisy-le-Grand
http://www.mia-software.com
.: model driven agility :._______________________________________________
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
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
