> 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.
Ok, so, to be explicit, (I checked after your quick response, which I
appreciate) I guess you were in the first three or four milestones before
aggregation broke and I disabled your file. You were not in M6, not in M7,
and now not in RC1. You haven't changed since Indigo, though obviously your
dependencies have. And, you, and your PMC, still feel confident you can get
all this worked out and well tested "in a few days"? Doesn't sound in the
spirit of the Simultaneous Release, to me ... but, admit I'm not that
familiar with Amp. But ... to miss such significant checkpoints sounds like
you may want to adopt the "release when you are ready model" and not worry
about expending the extra effort that is needed (by us all) to "stay
simultaneous". [And, as an aside, "no changes since Indigo", sounds like
not even bug fixes ... so you have either some incredibly solid and stable
code ... or ... well, "stagnate" is too strong a word, but maybe a
quiescent project?]
Just a suggestion ... there's no shame in not being part of Simultaneous
Release if it doesn't fit your needs and resources ... but you are welcome
to be in Juno if you do feel confident you have the time to contribute to a
high quality Juno Release, or you can "rejoin" in Juno SR1, if that better
fits your schedule and business needs.
I hope my note comes across as constructive as intended and not judgmental,
as I'm the first to admit there are all kinds of projects at Eclipse and in
the Simultaneous Release and its really up to the committers and adopters
to know what's needed and what they want.
Thanks again for keeping us informed and contributing to Eclipse. Good
luck,
From: Miles Parker <miles.par...@tasktop.com>
To: Cross project issues <cross-project-issues-dev@eclipse.org>,
Date: 05/23/2012 10:00 PM
Subject: Re: [cross-project-issues-dev] Juno RC1 staging repository is
complete
Sent by: cross-project-issues-dev-boun...@eclipse.org
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@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
______________________________
Miles T. Parker
Senior Engineer and Product Manager, Tasktop
http://tasktop.com
Committer, Eclipse Mylyn and Virgo
Project Lead, Model Focussing Tools and AMP
http://milesparker.blogspot.com
skype: milestravisparker
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
<<inline: graycol.gif>>
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
