Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Status and readiness for Kepler M1

Back to someone's earlier question, yes, for me this is a bit of a silent protest. CDT has never contributed to an M1 build. We're too busy with vacations or working on SR-1 of the previous release. That was fine because we were always enabled and picked up the final bits from the previous release. I'm not pleased by this, and yes it's late, but then that's why it shouldn't have been done to begin with (not so silent any more ;).


From: <Oberhuber>, Martin <Martin.Oberhuber@xxxxxxxxxxxxx>
Reply-To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: Wednesday, 22 August, 2012 9:17 AM
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] Status and readiness for Kepler M1

In fact I’ve enjoyed my vacation not checking Eclipse mailing lists recently J


I’m going to enable the tm.b3aggrcon and tcf.b3aggrcon as soon as my SSH access to is back





From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Wednesday, August 22, 2012 7:10 AM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: [cross-project-issues-dev] Status and readiness for Kepler M1


Still 26 projects not enabled for Kepler M1.

Can some one explain to me what this is about? Some passive aggressive protest? Too many people take vacation all summer and don't even check Eclipse mailing lists?
Are projects just indecisive and think a commitment now means it is a written in stone promise (which is never the case).
I know one or two people have mentioned they have special problems that will likely prevent participation in M1, but,
If I hear nothing, I'll assume the remaining 24 or so are dropping out, and will remove those files from the 'master'  branch.
For those projects to rejoin later will take an exception since there's a requirement for those participating to "keep participating" or else inform us all you no longer plan to.
The M4 deadline only applies to branch new projects, others (in previous release) expected to be in M1.

I should emphasize, if people do not want to be in sim. release, that's fine. It is a voluntary choice, and does take some amount of extra work. So, it doesn't mean you are a "bad project" or anything if you decide not to.
But, it is only common courtesy to keep us informed explicitly.

amp.b3aggrcon -
cdt.b3aggrcon -
dltk.b3aggrcon -
emf-query2.b3aggrcon -
emft-ecoretools.b3aggrcon -
emft-eef.b3aggrcon -
emft-egf.b3aggrcon -
emft-emffacet.b3aggrcon -
epp-mpc.b3aggrcon -
gmp-gmf-tooling.b3aggrcon -
gyrex.b3aggrcon -
jwt.b3aggrcon -
mat.b3aggrcon -
mdt-modisco.b3aggrcon -
mdt-papyrus.b3aggrcon -
mft.b3aggrcon -
mylyn-docs-intent.b3aggrcon -
pdt.b3aggrcon -
rap.b3aggrcon -
recommenders.b3aggrcon -
rtp.b3aggrcon -
scout.b3aggrcon -
soa-bpel.b3aggrcon -
soa-sca.b3aggrcon -
tcf.b3aggrcon -
tm.b3aggrcon -

Back to the top