On Mon, Dec 16, 2013 at 1:17 PM, Igor Fedorenko <[email protected]> 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=q&ofs=10 > [2] http://git.eclipse.org/c/sisu/org.eclipse.sisu.inject.git/ > stats/?period=q&ofs=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 [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
