[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] Votes and Staging Repo Expirations
|
I've just an exchange with Brian Fox whose CTO of Sonatype. He confirms the ejb staged binaries were deleted due to expiration and they've had to start cracking down on the 30-day period due to starved resources. I did not ask about the messy state of the staging repo overall.
What this means for us is that we need new builds of:
- jakarta.ejb-api
- jakarta.jws-api
- jakarta.enterprise.deploy-api
The above are either gone already or will be gone by Monday. If we do not get these up, there is no hope of a Jakarta EE 8 vote on Monday.
I'll do EJB. Kevin if you can redo jakarta.enterprise.deploy-api, that'd be awesome.
That leaves us with jakarta.jws-api. How will we get that one up?
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852
> On Aug 23, 2019, at 1:23 PM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
>
> I've done a detailed analysis of the effect of the 30 day expiration on our votes in progress. Published dates are from Nexus.
>
> - https://docs.google.com/spreadsheets/d/1_ujGiLDixJWUvwbBZbw7CRlsaujZl3j6TlMaljbbVIE/edit#gid=0
>
> We're going to find out Monday if the 30 expiration is real or imaginary as the binaries in PR #65 Jakarta Deployment are set to expire.
>
> If it is real, there are 4 more at-risk votes which will either need to end early or we will have to ask those people to recreate their binaries.
>
> The items in yellow will have a very short window for us to publish before they expire.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
> 310-633-3852
>
