[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

[cross-project-issues-dev] Trace Compass participation in Neon

[Marc-André Laperle]

Hi,

The Trace Compass project will participate in the
Neon simultaneous release train with a offset of +3 and version 2.0.0.

https://projects.eclipse.org/projects/tools.tracecompass/releases/2.0.0

Regards,
Marc-Andre Laperle
___
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] participation in Neon

[Thomas Watson]

I did create on: 
https://projects.eclipse.org/projects/rt.equinox/releases/4.6.0-neon

Unless you are talking about something else.  I still have to fill in the 
details of the release plan but I figured the release record at that URL 
was good enough to declare intent.

Tom





From:   David M Williams/Raleigh/IBM@IBMUS
To: Cross project issues 
Date:   10/21/2015 11:25 AM
Subject:Re: [cross-project-issues-dev] participation in Neon
Sent by:cross-project-issues-dev-boun...@eclipse.org



Maybe it is obvious, but I have a feeling that Wayne would wish I would 
have reminded everyone to create a release record, to go along with your 
announcements. :) 

I am lucky and never have ... but appears the "how to" instructions have 
moved to 

https://www.eclipse.org/projects/handbook/#pmi-releases

Thanks, 





From:Thomas Watson/Austin/IBM@IBMUS
To:"Cross project issues" , 
Date:10/21/2015 11:29 AM
Subject:[cross-project-issues-dev] Equinox participation in Neon
Sent by:cross-project-issues-dev-boun...@eclipse.org



Equinox will be participating in the Neon Simultaneous release with an 
offset 0.

The planned release is 4.6.0.

Tom

___
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"?

[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

[cross-project-issues-dev] SOA BPEL Designer, SOA.BPMN2 Modeler & MDT.BPMN2 participation in Neon

[Bob Brodt]

Hey all,

Better late than never, right?
These projects will be participating in Neon:

SOA BPEL Designer - offset +1
SOA BPMN2 Modeler - offset +2
MDT BPMN2 metamodel - offset 0


-- 

Robert ("Bob") Brodt
Senior Software Engineer
JBoss by Red Hat
___
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] participation in Neon

[David M Williams]

Maybe it is obvious, but I have a feeling that Wayne would wish I would 
have reminded everyone to create a release record, to go along with your 
announcements. :) 

I am lucky and never have ... but appears the "how to" instructions have 
moved to 

https://www.eclipse.org/projects/handbook/#pmi-releases

Thanks, 





From:   Thomas Watson/Austin/IBM@IBMUS
To: "Cross project issues" , 
Date:   10/21/2015 11:29 AM
Subject:[cross-project-issues-dev] Equinox participation in Neon
Sent by:cross-project-issues-dev-boun...@eclipse.org



Equinox will be participating in the Neon Simultaneous release with an 
offset 0.

The planned release is 4.6.0.

Tom

___
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] participation in Neon

[Wayne Beaton]

Thanks for providing the pointer to the shiny new Eclipse Project Handbook.

My apologies for not paying closer attention to this list; I've been 
distracted by some other things these past few weeks.


I'll go through the messages and update the Neon participation page 
accordingly.


Wayne

On 21/10/15 12:24 PM, David M Williams wrote:
Maybe it is obvious, but I have a feeling that Wayne would wish I 
would have reminded everyone to create a release record, to go along 
with your announcements. :)


I am lucky and never have ... but appears the "how to" instructions 
have moved to


https://www.eclipse.org/projects/handbook/#pmi-releases

Thanks,





From: Thomas Watson/Austin/IBM@IBMUS
To: "Cross project issues" ,
Date: 10/21/2015 11:29 AM
Subject: [cross-project-issues-dev] Equinox participation in Neon
Sent by: cross-project-issues-dev-boun...@eclipse.org




Equinox will be participating in the Neon Simultaneous release with an 
offset 0.


The planned release is 4.6.0.

Tom

___
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


--
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"?

[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

[cross-project-issues-dev] Disk usage report for Hudson/Build

[genie]

Compiled 2015-10-21T12:07

 build.eclipse.org 
-> Usage exceeding 1GB for: Hudson master jobs and workspace (2015-10-21T10:00)
   2.8G papyrus-trunk-nightly
   1.9G emf-cdo-maintenance
   1.7G papyrus-trunk-extra-nightly
   1.5G emf-cdo-integration
-> Usage exceeding 1GB for: /shared (1000G capacity) (2015-10-21T10:00)
 631.6G hipp
 158.6G rt
 115.7G eclipse
  46.7G technology
  32.9G webtools
  23.6G cbi
  23.1G SLES
  19.6G common
  13.4G jobs
  11.6G tools
   6.7G cbi-ng
   5.9G orbit
   5.3G modeling
   4.9G simrel
   1.6G mylyn
   1.4G soa
-> Usage exceeding 1GB for: /shared/modeling
   3.1G build
-> Usage exceeding 1GB for: /shared/tools
   4.6G tm
   2.7G objectteams
   1.4G mtj
   1.1G aspectj
-> Usage exceeding 1GB for: /shared/technology
  18.6G epp
  12.3G sapphire
   4.8G stem
   4.4G babel
   2.4G cosmos
   1.6G m2e
 END: build.eclipse.org 


 hudson-slave1.eclipse.org 
/dev/xvda1158G   24G  134G  15% /
-> Usage exceeding 1GB for: Hudson workspace on hudson-slave1 (50G capacity) 
(2015-10-20T21:00)
 END: hudson-slave1.eclipse.org 


 hudson-slave2.eclipse.org 
-> Usage exceeding 1GB for: 
 END: hudson-slave2.eclipse.org 


 hudson-slave3.eclipse.org 
/dev/xvda1 55G   23G   33G  41% /
-> Usage exceeding 1GB for: Hudson workspace on hudson-slave3 (50G capacity) 
(2015-10-20T18:00)
 END: hudson-slave3.eclipse.org 

___
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

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

[David M Williams]

Since no response from Birt, I have disabled BIRT from the aggregation, 
for now (which required me to also disable MAT chart feature, for now, 
since depends on BIRT)  so that we can see who else might still depend on 
compatibility bundle. 

According to my local builds, I think PTP does? 

If so, please correct soon, please ... I'd like to know if there's any 
more, after that is fixed? 

Thanks! 




From:   David M Williams/Raleigh/IBM@IBMUS
To: Cross project issues , 
Date:   10/20/2015 03:02 PM
Subject:Re: [cross-project-issues-dev] ... runtime compatibility 
bundle ... and LDT ... and Neon M3
Sent by:cross-project-issues-dev-boun...@eclipse.org



OK, ready to try again? Since the LDT contribution has not changed, I have 
disabled it from the aggregation build, so that we can see who else still 
refers to the defunct compatibility runtime bundle.

According to my local builds, BIRT will be the next project to fail ... 
now that DTP has been fixed (thanks Konstantin, and others). 
[Correction

Please correct any failures as soon as possible. That is, don't wait until 
your +N day. You can always contribute your final content later, but build 
"breaks" should be corrected right away. 

Same goes for you, LDT team, though I know your "break" isn't obvious, and 
realize you have some "redesign" work to do to figure out how to deliver 
"just your code" (and not all dependencies too). 

Thanks all, 





From:David M Williams/Raleigh/IBM@IBMUS
To:Cross project issues , 
Date:09/30/2015 11:04 AM
Subject:Re: [cross-project-issues-dev] DTP for Neon stream ... 
runtime.compatibility ... and LDT? ... and Neon M2
Sent by:cross-project-issues-dev-boun...@eclipse.org



OK, I give up. 

It appears some projects are not going to be able to react to the removal 
of runtime.compatibility bundle, for M2, so I have re-enabled the LDT 
contribution. (Bug 478009 and Bug 478330).
This will allow the aggregation build, at least, to complete, so that 
others can make progress. 

This won't help projects who have a direct dependancy on, say, DTP (which 
in turn as a dependency on runtime compatibility bundle) since they depend 
on it, but do not provide it. 
For those people, the only work around I know of is to "include" only that 
bundle from our M1 repository, or something similar. 
Less that ideal, but I'd like to push forward and see if we can get out 
some form of M2 that can be used to create a cleaner M3! 

Let me know if suggestions or alternative approaches. (And, FYI, it does 
not appear that extending the deadline a few days will help with the 
runtime compatibility issue, but, if anyone has been blocked due to this 
issue, and needs a few days to work around the problem, I think it 
reasonable to consider an extension of a few days ... if you make such a 
request, please be specific ... I'd hate to extend it to Monday instead of 
Friday (let's say) and then that still not be enough time.) 

Thanks, 




From:David M Williams/Raleigh/IBM@IBMUS
To:Cross project issues , 
Date:09/28/2015 08:47 PM
Subject:Re: [cross-project-issues-dev] DTP for Neon stream ... 
runtime.compatibility ... and LDT? ... and Neon M2
Sent by:cross-project-issues-dev-boun...@eclipse.org



I hope everyone remembers that Neon M2 is this Friday ... and that means 
your Neon M2 contributions must be done by Wednesday. 

AND .. it seems, some have not yet reacted to the platform removing 
org.eclipse. runtime.compatibility bundle (Bug 394739). 

AND .. some have been "getting it automatically" from the current Sim. 
Release contributions, because Lua Development Tools (LDT) duplicates it 
(and many others) in their repository (Bug 478009). 

Since LDT has not updated their repo yet for Neon, I fear some may have of 
a false sense that "everything is ok".

Put more bluntly, we all know, some projects do not build against the 
latest version of their pre-reqs! And, we all know that some projects 
won't react until "the build fails". 

Therefore ... I am about to make the build fail for others, by removing 
LDT's massive contribution. 

If someone has a better suggestion, that would be good to hear, but I hope 
I am doing everyone a favor, by making the problem more apparent in the 
aggregation build. 

(And, greatest thanks to those of you who HAVE reacted to this change 
already ... thanks to all your release engineers!) 

Thank to you all, 






From:David M Williams/Raleigh/IBM@IBMUS
To:Cross project issues , 
Date:09/21/2015 08:09 PM
Subject:Re: [cross-project-issues-dev] DTP for Neon stream ... and 
LDT?
Sent by:cross-project-issues-dev-boun...@eclipse.org



> A question regarding the aggregation build. I thought it was 
> designed to catch issues 

[cross-project-issues-dev] Sirius participating in Neon

[Pierre-Charles David]

Hi,

Sirius will be participating in the Neon Simultaneous release with an 
offset +3.


We plan to contribute version 4.0:
https://projects.eclipse.org/projects/modeling.sirius/releases/4.0.0

Regards,
Pierre-Charles
___
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