Re: [cross-project-issues-dev] m2e ponders participation in luna
Wayne, Which parts of m2e are required to carry incubating label, only feature and bundles that *include* Aether and Sisu or everything that makes use of Aether and Sisu (which is entire m2e)? I couldn't find any wiki that explains how to brand projects that consume incubating components. -- Regards, Igor On 12/16/2013, 12:45, Wayne Beaton wrote: FWIW, if m2e depends on the specific version of Maven that includes Sisu and Aether, including that version of Maven in the project downloads means that the downloads must be marked as incubating. By extension, any Eclipse package that includes m2e would have to be similarly-marked. Note that this does not mean that m2e itself needs to be moved back into an Incubation phase. ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] m2e ponders participation in luna
FWIW, we have a dependency to m2e runtime. With m2e’s move to 1.5 and switching from Sonatype Aether to Eclipse Aether Incubation we have a similar issue. We can fall back to the 1.4 maven runtime, though. A release of Eclipse Aether (this component contains 98% of what we need) would help - but I’ve no insight into Eclipse Aether release plans [1]. [1] http://www.eclipse.org/projects/project-plan.php?planurl=/aether/plan/current.xml Am 16.12.2013 um 05:06 schrieb Igor Fedorenko i...@ifedorenko.com: Hello, I just pushed updated version of m2e 1.5 plan.xml to our git repository [1]. I will let technology pmc and other eclipse powers decide if this is good enough for m2e to stay in simultaneous release. Also, in line with our use latest released maven recurring theme, we updated m2e to include maven 3.1.1 earlier this year and there is a 50/50 chance will update to maven 3.1.2, provided it is released before luna ip deadline. Problem is, maven 3.1.x includes Eclipse Aether and Eclipse Sisu binaries, both currently under incubation as eclipse technology project. My questions are Can m2e get an exception to ship incubating components in a mature project on the grounds that m2e includes released maven version, which just happens to include eclipse incubating project binaries? If m2e has to go back to incubation, will java and java ee epp package maintainers be willing to keep m2e in? [1] http://git.eclipse.org/c/www.eclipse.org/m2e.git/commit/?id=6c18b3cf58143f5f462f2f3b601ef2996887ef07 -- Regards, Igor ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] m2e ponders participation in luna
On 15/12/2013 11:06 PM, Igor Fedorenko wrote: Problem is, maven 3.1.x includes Eclipse Aether and Eclipse Sisu binaries, both currently under incubation as eclipse technology project. What I don't understand is that if these projects are mature enough to be included in production versions of Maven, why don't you simply ask the projects to do a Release Review to get to Mature status? It's not that much work. -- Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] m2e ponders participation in luna
On Mon, Dec 16, 2013 at 1:17 PM, Igor Fedorenko i...@ifedorenko.com wrote: On 12/16/2013, 4:16, Mike Milinkovich wrote: On 15/12/2013 11:06 PM, Igor Fedorenko wrote: Problem is, maven 3.1.x includes Eclipse Aether and Eclipse Sisu binaries, both currently under incubation as eclipse technology project. What I don't understand is that if these projects are mature enough to be included in production versions of Maven, why don't you simply ask the projects to do a Release Review to get to Mature status? It's not that much work. I am not sure if the two projects pass diversity criterion, see [1] and [2] git stats for example. Even if the two projects do get their respective mature release in next few weeks, this will not give us enough time to integrate them into Maven, release new version of Maven and integrate the new version of Maven into m2e before Luna IP deadline, which I assume is in two months or so. [1] http://git.eclipse.org/c/aether/aether-core.git/stats/?period=qofs=10 [2] http://git.eclipse.org/c/sisu/org.eclipse.sisu.inject.git/ stats/?period=qofs=10 last year the IP log deadline for Kepler was on May 24 http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg08897.html -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] m2e ponders participation in luna
Wasn't there another deadline in February for new CQ submissions? -- Regards, Igor On 12/16/2013, 9:36, Matthias Sohn wrote: On Mon, Dec 16, 2013 at 1:17 PM, Igor Fedorenko i...@ifedorenko.com mailto:i...@ifedorenko.com wrote: On 12/16/2013, 4:16, Mike Milinkovich wrote: On 15/12/2013 11:06 PM, Igor Fedorenko wrote: Problem is, maven 3.1.x includes Eclipse Aether and Eclipse Sisu binaries, both currently under incubation as eclipse technology project. What I don't understand is that if these projects are mature enough to be included in production versions of Maven, why don't you simply ask the projects to do a Release Review to get to Mature status? It's not that much work. I am not sure if the two projects pass diversity criterion, see [1] and [2] git stats for example. Even if the two projects do get their respective mature release in next few weeks, this will not give us enough time to integrate them into Maven, release new version of Maven and integrate the new version of Maven into m2e before Luna IP deadline, which I assume is in two months or so. [1] http://git.eclipse.org/c/__aether/aether-core.git/stats/?__period=qofs=10 http://git.eclipse.org/c/aether/aether-core.git/stats/?period=qofs=10 [2] http://git.eclipse.org/c/sisu/__org.eclipse.sisu.inject.git/__stats/?period=qofs=10 http://git.eclipse.org/c/sisu/org.eclipse.sisu.inject.git/stats/?period=qofs=10 last year the IP log deadline for Kepler was on May 24 http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg08897.html -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] m2e ponders participation in luna
On 16/12/2013 9:39 AM, Igor Fedorenko wrote: Wasn't there another deadline in February for new CQ submissions? I _think_ that's for new dependencies, not a new version of an existing dependency. But Wayne or Janet are the experts. -- Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] m2e ponders participation in luna
The submission deadline is the deadline for all CQs. The May deadline was for IP log submission. I agree that if Sisu and Aether have both been adopted by a release version of Maven, that this is a pretty clear indication that they are mature technology. Have the Sisu and Aether projects been contacted regarding graduation? I'd love to hear their opinion regarding their readiness. If, theoretically, we could get Sisu and Aether to graduate early in the new year, is it possible to create a new release of Maven based on the 1.0 code in time for the simultaneous release? FWIW, if m2e depends on the specific version of Maven that includes Sisu and Aether, including that version of Maven in the project downloads means that the downloads must be marked as "incubating". By extension, any Eclipse package that includes m2e would have to be similarly-marked. Note that this does not mean that m2e itself needs to be moved back into an Incubation phase. Wayne On 12/16/2013 10:39 AM, Mike Milinkovich wrote: On 16/12/2013 9:39 AM, Igor Fedorenko wrote: Wasn't there another deadline in February for new CQ submissions? I _think_ that's for new dependencies, not a new version of an existing dependency. But Wayne or Janet are the experts. -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundation Learn about Eclipse Projects ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] m2e ponders participation in luna
I cannot speak for them but m2e is included in my RCP/RAP package, too. I don't like the idea of having to use an Incubation label on my package, and I am sure that the Java and Java EE package maintainers have a similar opinion. Thanks, Markus On Mon, Dec 16, 2013 at 7:13 PM, Igor Fedorenko i...@ifedorenko.com wrote: On 12/16/2013, 12:45, Wayne Beaton wrote: The submission deadline is the deadline for all CQs. The May deadline was for IP log submission. I agree that if Sisu and Aether have both been adopted by a release version of Maven, that this is a pretty clear indication that they are mature technology. Have the Sisu and Aether projects been contacted regarding graduation? I'd love to hear their opinion regarding their readiness. If, theoretically, we could get Sisu and Aether to graduate early in the new year, is it possible to create a new release of Maven based on the 1.0 code in time for the simultaneous release? FWIW, if m2e depends on the specific version of Maven that includes Sisu and Aether, including that version of Maven in the project downloads means that the downloads must be marked as incubating. By extension, any Eclipse package that includes m2e would have to be similarly-marked. Note that this does not mean that m2e itself needs to be moved back into an Incubation phase. What do java and java ee epp package maintainers think about incubating label? -- Regards, Igor ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] m2e ponders participation in luna
On 16 Dec 2013, at 17:45, Wayne Beaton wa...@eclipse.org wrote: Have the Sisu and Aether projects been contacted regarding graduation? I'd love to hear their opinion regarding their readiness. The plan was to make two further releases of Sisu from the incubator before requesting to graduate next year (sometime late Q1?) but we could ask to graduate early if absolutely necessary. ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] m2e ponders participation in luna
Hi There is a workaround for 'incubation' within mature projects. New optional experimental functionality may be shipped in examples plugins. Regards Ed Willink On 16/12/2013 04:06, Igor Fedorenko wrote: Hello, I just pushed updated version of m2e 1.5 plan.xml to our git repository [1]. I will let technology pmc and other eclipse powers decide if this is good enough for m2e to stay in simultaneous release. Also, in line with our use latest released maven recurring theme, we updated m2e to include maven 3.1.1 earlier this year and there is a 50/50 chance will update to maven 3.1.2, provided it is released before luna ip deadline. Problem is, maven 3.1.x includes Eclipse Aether and Eclipse Sisu binaries, both currently under incubation as eclipse technology project. My questions are Can m2e get an exception to ship incubating components in a mature project on the grounds that m2e includes released maven version, which just happens to include eclipse incubating project binaries? If m2e has to go back to incubation, will java and java ee epp package maintainers be willing to keep m2e in? [1] http://git.eclipse.org/c/www.eclipse.org/m2e.git/commit/?id=6c18b3cf58143f5f462f2f3b601ef2996887ef07 -- Regards, Igor ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] m2e ponders participation in luna
Hi David Yes. I wrote 'optional', so it is obviously not Core. Regards Ed Willink On 16/12/2013 07:17, David M Williams wrote: I'm not sure if I should laugh, or cry? If they are true examples, those example components could just be omitted without loss of core functionality, right? Even then, I guess I've not read the guide lines that say incubating examples can be released without an incubating label (since incubating refers to a project, not a component?). I hope this workaround is not simply a way to work around the release rules established by the Eclipse Foundation ... since I think we all know what that means ... after all, as committers, don't we agreed to abide by those rules? But, I'm sure Ed meant something else than the way I am reading it. From: Ed Willink e...@willink.me.uk To: Cross project issues cross-project-issues-dev@eclipse.org, Date: 12/16/2013 01:36 AM Subject: Re: [cross-project-issues-dev] m2e ponders participation in luna Sent by: cross-project-issues-dev-boun...@eclipse.org Hi There is a workaround for 'incubation' within mature projects. New optional experimental functionality may be shipped in examples plugins. Regards Ed Willink On 16/12/2013 04:06, Igor Fedorenko wrote: Hello, I just pushed updated version of m2e 1.5 plan.xml to our git repository [1]. I will let technology pmc and other eclipse powers decide if this is good enough for m2e to stay in simultaneous release. Also, in line with our use latest released maven recurring theme, we updated m2e to include maven 3.1.1 earlier this year and there is a 50/50 chance will update to maven 3.1.2, provided it is released before luna ip deadline. Problem is, maven 3.1.x includes Eclipse Aether and Eclipse Sisu binaries, both currently under incubation as eclipse technology project. My questions are Can m2e get an exception to ship incubating components in a mature project on the grounds that m2e includes released maven version, which just happens to include eclipse incubating project binaries? If m2e has to go back to incubation, will java and java ee epp package maintainers be willing to keep m2e in? [1] http://git.eclipse.org/c/www.eclipse.org/m2e.git/commit/?id=6c18b3cf58143f5f462f2f3b601ef2996887ef07 -- Regards, Igor ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
