[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

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, 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

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'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

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

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 ___

Re: [cross-project-issues-dev] participation in Neon

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

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] SOA BPEL Designer, SOA.BPMN2 Modeler & MDT.BPMN2 participation in Neon

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

Re: [cross-project-issues-dev] participation in Neon

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

Re: [cross-project-issues-dev] participation in Neon

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

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:

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

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

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

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

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

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.

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

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

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

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

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

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