|Re: [cross-project-issues-dev] Announcing participation in Neon|
Looking at the Simultaneous Release Requirements document 
I see we should add a link to the release record when announcing which I didn't do.
The list of participating project  does show CDT but not its version/release record so here it is:
Also, CDT has traditionally been +1 (unlike what is in the list ).
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [cross-project-issues-dev-bounces@xxxxxxxxxxx] on behalf of Wayne Beaton [wayne@xxxxxxxxxxx]
Sent: October 27, 2015 1:03 AM
To: Cross project issues
Subject: [cross-project-issues-dev] Announcing participation in Neon
It's that time of year! The opt-in deadline for Neon is M4 on December 18. Opt-in early! Avoid the rush!
We decided a few years ago to require every project that's participating in the release to explicitly opt-in to participation. This was done primarily because we always ended up with a handful of projects that carried over from a previous year, but didn't pay attention to the communication (I believe that in most cases, the projects didn't have representation on this list). By making project teams opt-in explicitly, we had a means of finding out early if had to chase somebody down.
The requirements for participation are documented in the Simultaneous Release Requirements document . For good measure, I also added them to the new Eclipse Project Handbook .
The short version is: make a release record in the PMI and announce your plan on this list along with your offset. I take it from there. Note that you can change the version number that you use on the release record and everything will just work (if, for example, you're not sure then just pick a number and change it when you are sure).
I'm assembling the list of participating projects here:
If your project is not listed, or any of the information is wrong, let me know (either by direct communication or via this list).