| Re: [jakarta.ee-spec.committee] Votes and Staging Repo Expirations |
On the current issues, here are the binaries already deleted: - https://oss.sonatype.org/content/repositories/staging/jakarta/enterprise/deploy/jakarta.enterprise.deploy-api/1.7.2/ The non-tool option for that is to re-roll the release. Here are the binaries that will be deleted before the vote completes: - https://oss.sonatype.org/content/repositories/staging/jakarta/transaction/jakarta.transaction-api/1.3.3/ - https://oss.sonatype.org/content/repositories/staging/jakarta/json/bind/jakarta.json.bind-api/1.0.2/ - https://oss.sonatype.org/content/repositories/staging/jakarta/xml/rpc/jakarta.xml.rpc-api/1.1.4/ - https://oss.sonatype.org/content/repositories/staging/jakarta/servlet/jsp/jakarta.servlet.jsp-api/2.3.6/ The non-tool option for these is to conclude the votes early and publish them by Friday August 30th. I would add websockets in that list as these binaries expire within 24-48 hours after vote completion. - https://oss.sonatype.org/content/repositories/staging/jakarta/websocket/jakarta.websocket-all/1.1.2/ - https://oss.sonatype.org/content/repositories/staging/jakarta/websocket/jakarta.websocket-api/1.1.2/ - https://oss.sonatype.org/content/repositories/staging/jakarta/websocket/jakarta.websocket-client-api/1.1.2/ Is this what we want to do? If so, we'd need to make this recommendation to the Steering Committee tomorrow. -David