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

[Wenz, Michael]

Hi all,

I do not see Graphiti appear in the list of participating projects, so I just 
repeat my mail back from August:

Michael

>Hi all,
>
>Graphiti will be participating in the Eclipse Neon Simultaneous release with 
>an offset of +3.
>
>We will contribute Graphiti 0.13.0 to Eclipse Neon:
>https://projects.eclipse.org/projects/modeling.graphiti/releases/0.13.0
>
>Michael



From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of David M 
Williams
Sent: Mittwoch, 21. Oktober 2015 16:01
To: cross-project-issues-dev@eclipse.org
Subject: [cross-project-issues-dev] Did I mess up our procedure for Neon? With 
respect to declaring, and enablement, and our "list of participants"?

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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Max Rydahl Andersen]

On 21 Oct 2015, at 19:01, Gunnar Wagenknecht wrote:


David,

That brings up a good question ... The Gyrex project will continue to 
participate in the release train, but we'll no longer contribute to 
the release train repo.


may i ask why ?



-Gunnar


--
Gunnar Wagenknecht
gun...@wagenknecht.org, http://guw.io/






Am 21.10.2015 um 07:01 schrieb David M Williams 
:


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@eclipse.org
To change your delivery options, retrieve your password, or 
unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
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

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



/max
http://about.me/maxandersen
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Efftinge, Sven]

Here are the release records:

Xtext 2.11.0 -
https://projects.eclipse.org/projects/modeling.tmf.xtext/releases/2.11.0
MWE 2.9.0 -
https://projects.eclipse.org/projects/modeling.emf.mwe/releases/2.9.0
Xpand 2.1.1 -
https://projects.eclipse.org/projects/modeling.m2t.xpand/releases/2.1.1

2015-10-23 21:24 GMT+02:00 Wayne Beaton :

> Maybe you can make some educated guesses regarding versions and create
> records for them (that you can change later).
>
> And by maybe, I mean "please do"
>
> Thanks,
>
> Wayne
>
>
> On 22/10/15 02:33 AM, Efftinge, Sven wrote:
>
> 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 clear yet what version we will have released by then.
>
> Regards,
> Sven
>
> 2015-10-22 6:14 GMT+02:00 Ed Merks :
>
>> David,
>>
>> I suppose it's hard to disable EMF and still have a Platform.  Even
>> disabling XSD would presumably disable WTP.
>>
>> I think most of us make an assumption that the projects on the train
>> last  year, particularly projects on which we might depend, will be on the
>> train next year.  Participation kind of needs to be a binding long term
>> commitment to remain on the train, especially for non-leaf projects.  In
>> that case, it's probably more significant to announce withdrawal of
>> participation as that has impact on downstream project participation.
>>
>> In any case, EMF and XSD will be participating in Neon:
>>
>> https://projects.eclipse.org/projects/modeling.emf.emf/releases/2.12.0
>>
>> EMF Base is at offset -2
>> EMF Core is at offset +1
>>
>> https://projects.eclipse.org/projects/modeling.mdt.xsd/releases/2.12.0
>>
>> XSD is at offset +1
>>
>>
>>
>>
>>
>> On 21/10/2015 4:01 PM, 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, 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 listcross-project-issues-...@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe from 
>> this list, 
>> visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>>
>>
>> ___
>> 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
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> --
> Wayne Beaton
> @waynebeaton
> The Eclipse Foundation
> [image: EclipseCon Europe 2015] 
>
> ___
> 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
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Gunnar Wagenknecht]

> Am 24.10.2015 um 07:56 schrieb Max Rydahl Andersen :

>> That brings up a good question ... The Gyrex project will continue to 
>> participate in the release train, but we'll no longer contribute to the 
>> release train repo.
> 
> may i ask why ?

We only contribute(d) "Target Components". It's easier for us (also from a 
support/maintenance perspective) to direct people to reference the repositories 
directly in their target platforms. It's also significant faster to load a 
smaller repo then composites. :)

-Gunnar
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Wayne Beaton]

Please create a release record.

Thanks!

Wayne

On 22/10/15 09:19 AM, Fred Bricon wrote:

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
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




--
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5


___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon Europe 2015 
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Wayne Beaton]

Please create a release record anyway. If you're not sure what the 
version number will be, make a good guess. I trust your good guesses.


FWIW, you can just change the version name on the record later and 
everything will work.


Wayne

On 22/10/15 08:58 AM, Greg Watson wrote:

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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon Europe 2015 
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Efftinge, Sven]

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 clear yet what version we will have released by then.

Regards,
Sven

2015-10-22 6:14 GMT+02:00 Ed Merks :

> David,
>
> I suppose it's hard to disable EMF and still have a Platform.  Even
> disabling XSD would presumably disable WTP.
>
> I think most of us make an assumption that the projects on the train last
> year, particularly projects on which we might depend, will be on the train
> next year.  Participation kind of needs to be a binding long term
> commitment to remain on the train, especially for non-leaf projects.  In
> that case, it's probably more significant to announce withdrawal of
> participation as that has impact on downstream project participation.
>
> In any case, EMF and XSD will be participating in Neon:
>
> https://projects.eclipse.org/projects/modeling.emf.emf/releases/2.12.0
>
> EMF Base is at offset -2
> EMF Core is at offset +1
>
> https://projects.eclipse.org/projects/modeling.mdt.xsd/releases/2.12.0
>
> XSD is at offset +1
>
>
>
>
>
> On 21/10/2015 4:01 PM, 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, 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 listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> ___
> 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
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Christian Campo]

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 issues 
>
Datum: Donnerstag, 22. Oktober 2015 um 08:33
An: Cross issues 
>
Betreff: 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 clear yet what version we will have released by then.

Regards,
Sven

2015-10-22 6:14 GMT+02:00 Ed Merks 
>:
David,

I suppose it's hard to disable EMF and still have a Platform.  Even disabling 
XSD would presumably disable WTP.

I think most of us make an assumption that the projects on the train last  
year, particularly projects on which we might depend, will be on the train next 
year.  Participation kind of needs to be a binding long term commitment to 
remain on the train, especially for non-leaf projects.  In that case, it's 
probably more significant to announce withdrawal of participation as that has 
impact on downstream project participation.

In any case, EMF and XSD will be participating in Neon:

https://projects.eclipse.org/projects/modeling.emf.emf/releases/2.12.0

EMF Base is at offset -2
EMF Core is at offset +1

https://projects.eclipse.org/projects/modeling.mdt.xsd/releases/2.12.0

XSD is at offset +1





On 21/10/2015 4:01 PM, 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, 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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

-
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de

Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
-
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Donát Csikós]

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:  on behalf of
> "Efftinge, Sven" 
> Antworten an: Cross issues 
> Datum: Donnerstag, 22. Oktober 2015 um 08:33
> An: Cross issues 
> Betreff: 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 clear yet what version we will have released by then.
>
> Regards,
> Sven
>
> 2015-10-22 6:14 GMT+02:00 Ed Merks :
>
>> David,
>>
>> I suppose it's hard to disable EMF and still have a Platform.  Even
>> disabling XSD would presumably disable WTP.
>>
>> I think most of us make an assumption that the projects on the train
>> last  year, particularly projects on which we might depend, will be on the
>> train next year.  Participation kind of needs to be a binding long term
>> commitment to remain on the train, especially for non-leaf projects.  In
>> that case, it's probably more significant to announce withdrawal of
>> participation as that has impact on downstream project participation.
>>
>> In any case, EMF and XSD will be participating in Neon:
>>
>> https://projects.eclipse.org/projects/modeling.emf.emf/releases/2.12.0
>>
>> EMF Base is at offset -2
>> EMF Core is at offset +1
>>
>> https://projects.eclipse.org/projects/modeling.mdt.xsd/releases/2.12.0
>>
>> XSD is at offset +1
>>
>>
>>
>>
>>
>> On 21/10/2015 4:01 PM, 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, 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 listcross-project-issues-...@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe from 
>> this list, 
>> visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>>
>>
>> ___
>> 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
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
> -
> compeople AG
> Untermainanlage 8
> 60329 Frankfurt/Main
> fon: +49 (0) 69 / 27 22 18 0
> fax: +49 (0) 69 / 27 22 18 22
> web: www.compeople.de
>
> Vorstand: Jürgen Wiesmaier
> Aufsichtsratsvorsitzender: Christian Glanz
>
> Sitz der Gesellschaft: Frankfurt/Main
> Handelsregister Frankfurt HRB 56759
> USt-IdNr. DE207665352
> -
>
> ___
> 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
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Andreas Sewe]

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, need to come up with a list of "those who
> have declared intent",
> and then I will disable the rest.

Quoting Marcel, who stated this back in August:

>> Code Recommenders will participate with version 2.3.x.
> 
> offset +3

That's still true.

Andreas

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Eike Stepper]

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 mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Greg Watson]

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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Fred Bricon]

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
> ___
> 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
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[David M Williams]

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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Gunnar Wagenknecht]

David,

That brings up a good question ... The Gyrex project will continue to 
participate in the release train, but we'll no longer contribute to the release 
train repo.

-Gunnar


-- 
Gunnar Wagenknecht
gun...@wagenknecht.org, http://guw.io/






> Am 21.10.2015 um 07:01 schrieb David M Williams :
> 
> 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@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Wayne Beaton]

I'll update the list.

Wayne

On 21/10/15 10:01 AM, David M Williams wrote:

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? 


--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon Europe 2015 
___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Marc Khouzam]

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


From: cross-project-issues-dev-boun...@eclipse.org 
[cross-project-issues-dev-boun...@eclipse.org] on behalf of Doug Schaefer 
[dschae...@qnx.com]
Sent: October 21, 2015 11:43 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? 
With respect to declaring, and enablement, and our "list of participants"?

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.

From: 
>
 on behalf of Thomas Watson >
Reply-To: Cross project issues 
>
Date: Wednesday, October 21, 2015 at 11:27 AM
To: Cross project issues 
>
Subject: Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? 
With respect to declaring, and enablement, and our "list of participants"?

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@eclipse.org
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-boun...@eclipse.org




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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Thomas Watson]

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@eclipse.org
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-boun...@eclipse.org



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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Doug Schaefer]

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.

From: 
>
 on behalf of Thomas Watson >
Reply-To: Cross project issues 
>
Date: Wednesday, October 21, 2015 at 11:27 AM
To: Cross project issues 
>
Subject: Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? 
With respect to declaring, and enablement, and our "list of participants"?

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@eclipse.org
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-boun...@eclipse.org




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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[David M Williams]

Thanks for letting us know, Gunnar. I'll remove your b3aggrcon file from 
master. 

You'll still need to do a release record. :) 





From:   Gunnar Wagenknecht 
To: Cross project issues , 
Date:   10/21/2015 01:02 PM
Subject:Re: [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-boun...@eclipse.org



David,

That brings up a good question ... The Gyrex project will continue to 
participate in the release train, but we'll no longer contribute to the 
release train repo.

-Gunnar


-- 
Gunnar Wagenknecht
gun...@wagenknecht.org, http://guw.io/






> Am 21.10.2015 um 07:01 schrieb David M Williams 
:
> 
> 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@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Ed Merks]

David,

I suppose it's hard to disable EMF and still have a Platform.  Even 
disabling XSD would presumably disable WTP.


I think most of us make an assumption that the projects on the train 
last  year, particularly projects on which we might depend, will be on 
the train next year.  Participation kind of needs to be a binding long 
term commitment to remain on the train, especially for non-leaf 
projects.  In that case, it's probably more significant to announce 
withdrawal of participation as that has impact on downstream project 
participation.


In any case, EMF and XSD will be participating in Neon:

https://projects.eclipse.org/projects/modeling.emf.emf/releases/2.12.0

EMF Base is at offset -2
EMF Core is at offset +1

https://projects.eclipse.org/projects/modeling.mdt.xsd/releases/2.12.0

XSD is at offset +1




On 21/10/2015 4:01 PM, 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, 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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Doug Schaefer]

:). 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.

From: 
>
 on behalf of Marc Khouzam 
>
Reply-To: Cross project issues 
>
Date: Wednesday, October 21, 2015 at 12:39 PM
To: Cross project issues 
>
Subject: Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? 
With respect to declaring, and enablement, and our "list of participants"?

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


From: 
cross-project-issues-dev-boun...@eclipse.org
 
[cross-project-issues-dev-boun...@eclipse.org]
 on behalf of Doug Schaefer [dschae...@qnx.com]
Sent: October 21, 2015 11:43 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? 
With respect to declaring, and enablement, and our "list of participants"?

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.

From: 
>
 on behalf of Thomas Watson >
Reply-To: Cross project issues 
>
Date: Wednesday, October 21, 2015 at 11:27 AM
To: Cross project issues 
>
Subject: Re: [cross-project-issues-dev] Did I mess up our procedure for Neon? 
With respect to declaring, and enablement, and our "list of participants"?

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@eclipse.org
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-boun...@eclipse.org




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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev