Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? With respect to declaring, and enablement, and our "list of participants"?

I think there was actually a mail last year that said, that projects from the previous year would participate automatically. In any case: Xtext intends to participate in Neon (offset +2) MWE intends to participate in Neon (offset +2) Xpand intends to participate in Neon (offset +2) It is not

Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? With respect to declaring, and enablement, and our "list of participants"?

Same here Riena will participate in Neon with offset+3. Version is 6.2. Regards christian Von: > on behalf of "Efftinge, Sven" > Antworten an:

[cross-project-issues-dev] Sphinx participation in Neon

Hi, The Sphinx project will participate in the Neon simultaneous release train. The offset is +3 and the contributed version of Sphinx will be 0.10.0. https://projects.eclipse.org/projects/modeling.sphinx/releases/0.10.0 Regards, Stephan ___

Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? With respect to declaring, and enablement, and our "list of participants"?

Buildship will participate in Neon with +1 offset and with version 2.0.0. Best regards, Donát 2015-10-22 8:37 GMT+02:00 Christian Campo : > Same here…. Riena will participate in Neon with offset+3. Version is 6.2. > > Regards > christian > > Von:

Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? With respect to declaring, and enablement, and our "list of participants"?

On 21.10.15 16:01, David M Williams wrote: > 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,

Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? With respect to declaring, and enablement, and our "list of participants"?

CDO will contribute its version 4.5.0 to Neon. The offset stays at +2. Oomph will contribute its version 1.4.0 to Neon. The offset stays at +3. Cheers /Eike http://www.esc-net.de http://thegordian.blogspot.com http://twitter.com/eikestepper

[cross-project-issues-dev] Memory Analzyer participation in Neon

The Memory Analyzer project (tools.mat) will participate in the Neon release train with a 1.6.0 release: https://projects.eclipse.org/projects/tools.mat/releases/1.6.0 As in previous years the project will have offset +3. Regards, Krum ___

Re: [cross-project-issues-dev] Next turn of the crank ... runtime compatibility bundle

Hi Eclipse Scout will be jumping on the release by Neon M4. We will activating the scout.b3aggrcon file then. scout-rap.b3aggrcon will be deleted as we do not deliver a rap ui anymore. Greetings Stephan -- Scout Release Engineer, Senior Software Architect **BSI** **Business Systems

Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? With respect to declaring, and enablement, and our "list of participants"?

PTP/Remote will be in Neon. Versions unknown at this point. Greg ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? With respect to declaring, and enablement, and our "list of participants"?

m2e will contribute version 1.7 (most likely) to Neon, with a +2 offset. Fred On Thu, Oct 22, 2015 at 8:58 AM, Greg Watson wrote: > > PTP/Remote will be in Neon. Versions unknown at this point. > > Greg > ___ >