Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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.


On Mon, Dec 16, 2013 at 7:13 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> 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?


cross-project-issues-dev mailing list

Back to the top