:). Thanks, Marc.
BTW, my point really is that I don’t think it should be so easy for projects to come and go on the release train. Assuming people are using the contributions of the project, it would be unsettling for them to be removed all of a sudden in the next release.
If the impact is small, then you need to ask whether they should have been on the train to begin with. Stuff happens, I get that. But something to think about. And probably a discussion for the planning council.
Doug.
We did declare CDT for Neon, referring to your now famous line :-)
"CDT will be in every simultaneous release from the first one until forever.
"
https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12209.html
A man after my own heart :).
I can’t remember if CDT declared for Neon. It’ll be a sad day the release we don’t.
Doug.
Not sure you noticed but Equinox only declared for Neon just now. Would have been interesting to see what happens if you disabled Equinox.
Tom
From: David M Williams/Raleigh/IBM@IBMUS
To: cross-project-issues-dev@xxxxxxxxxxx
Date: 10/21/2015 09:15 AM
Subject: [cross-project-issues-dev] Did I mess up our procedure for Neon? With respect to declaring, and enablement, and our "list of participants"?
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Just today I realized I think I was supposed to "disable" everyone, until they responded affirmatively that they were participating in Neon.
Since so many have declared their intent already, I hate to start over, by disabling everyone, but, need to come up with a list of "those who have declared intent",
and then I will disable the rest.
Wayne have you been keeping track? So far, the list at
https://projects.eclipse.org/releases/neon
only shows "Eclipse" is participating. I assume that's set to always be true. :)
But the rest need someone to enter the data?
If we can get a better list in next week or so, then by M3 I will disable anyone who has not yet declared intent.
For example, perhaps BIRT is no longer planning to participate? (For all I know?)
Thanks,
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|