Hi All, Am 16.12.2013 um 10:16 schrieb Mike Milinkovich <[email protected]>: > 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.
That’s clearly a valid option. I just want to clarify that there are two different things: 1. Participating in the release train 2. Distribution in the release train repo Both things do not represent the same set of Eclipse projects. We did have Eclipse projects in the previous releases which did not participate in the release train but ended up in the release train repo because they were a required dependency. They are treated like all other 3rd party dependencies from Orbit - just JAR files then end in the repo. It must be proper releases with an approved IP-log, though. But that is no different than what we expect for 3rd party dependencies from Orbit. HTH, Gunnar -- Gunnar Wagenknecht [email protected] _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
