> ... 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
What? Doug _quietly_ protesting?! Are
you mellowing-out? Or, probably just too busy to take the time. :)
Feel free to offer your views or counter
suggestions to the bug that started this change in process:
I agree, it has not gone well. I thought
it would be an extremely easy way to address the concerns raised in that
bug, but guess not. I'm not sure what else to suggest.
Doug Schaefer <dschaefer@xxxxxxx>
Cross project issues
08/22/2012 10:05 AM
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 ;).
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. http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Integrate_Early_and_Often
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.