Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-build] Coordinating component release plan with Glassfish release plan
Thanks - that is clear for me. Is the deadlone for promoting artifacts beyond staging?

On 26 October 2018 at 10:35, Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx> wrote:
Let me clarify. November 5th deadline is about uptake new Eclipse versions of dependencies and releasing artifacts to OSSRH *staging* so other projects can take it. I see that you’ve done it already. You are the first one! Congrats!. This is not about the public release. You don’t need to pass the release review in order to do it. But I am suggesting initiating the release review asap before the majority of projects do it. It will make Eclipse IP team life a bit easier.

Thanks,
Dmitry

On 25 Oct 2018, at 15:32, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:

Hi,

I just wanted to check something regarding the current glassfish release plan:

It has a date of November 5th but the JTA API 1.3.1 release review is not scheduled to conclude until November 7th:

Is that a problem?

I would add that the JTA API 1.3.1 release is already in Eclipse staging since yesterday and so I also have a PR to upgrade GlassFish (assuming GlassFish can build from dependencies in staging):

Thanks,
Tom
_______________________________________________
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


_______________________________________________
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


Back to the top