Still here, still sorting out dependency issues in my "spare" time. (This time w/ GEF3D.) AMP hasn't changed at all since Indigo, but everything else has. :) If I don't get them squashed by the end of this weekend I will formally withdraw it from Juno.
On 2012-05-23, at 6:51 PM, David M Williams wrote: Thanks to all the last minute fixes and getting a clean build. I've disabled the aggregation build and assume we are ready for RC1, unless someone comes up with a blocking problem that justifies a respin.
My main concern is that there are still two projects still disabled:
amp.b3aggrcon
riena.b3aggrcon
Riena I'm not worried about, I know they sort of "come and go" as are sensitive to exact platform version, so assuming this was an oversight or busy week for the Riena team and they are basically ok and will be back in for RC2.
Amp, on the other hand, has been disabled for nearly all of Juno, and its update site in the b3aggrcon file still points to a software repository named "indigo_b3" which sounds old.
I think maybe Amp has "dropped out" of Juno, and I have just missed that. The contact listed in file is Mile Parker. If I don't here from him soon, here on this list, or hear from the Modeling PMC, I'll assume they've withdrawn and remove the contribution file before RC2.
Thanks all,
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
______________________________ Miles T. Parker Senior Engineer and Product Manager, Tasktop Committer, Eclipse Mylyn and Virgo Project Lead, Model Focussing Tools and AMP
|
