[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ee4j-build] Missing artifacts in OSSRH staging
|
On 1/4/19 1:58 AM, Ed Bratt wrote:
I may be mistaken, but I think that all projects have been had their
release reviews completed and are approved. Dmitry, can you confirm?
Release review for Metro is pending[1]. It is started but not finished yet.
There are two things we're working on:
* jaxr (CQ for using "oracle" version of the dependency has been
approved[2])
* ibm jdk specific support - haven't heard back to my requests/questions
from no one on this list[3], no one from EF[4] nor from EMO yet (I sent
email directly to EMO yesterday)
thanks,
--lukas
[1]: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18274
[2]: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18389
[3]: https://www.eclipse.org/lists/ee4j-build/msg00575.html
[4]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=541848
-- Ed
On 1/3/2019 4:47 PM, Bill Shannon wrote:
Ed Bratt wrote on 1/3/19 3:56 PM> Another suggestion might be that we
start
promoting components that are ready,
over to Maven Central -- API JARs that have been tested and confirmed
working
might be the first set of components that can be promoted in
preparation for
final release. There might be other project artifacts that could be
considered
ready to release.
YES!!!
If the component has completed its Eclipse Release Review, and has
been tested
with the TCK and CTS, it should just be released to Maven Central.
There's no
reason to wait around for the rest of GlassFish.
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build
