Is there a set of instructions for the current publish process that I could/should review to bring myself back up to speed?
AdTHANKSvance! -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! ________________________________ From: Gary Gregory <garydgreg...@gmail.com> Sent: Saturday, April 1, 2023 3:03:28 PM To: Milamber <milam...@apache.org> Cc: Vladimir Sitnikov <sitnikov.vladi...@gmail.com>; Mukul Gandhi <muk...@apache.org>; dev@xalan.apache.org <dev@xalan.apache.org>; j-us...@xalan.apache.org <j-us...@xalan.apache.org>; priv...@xalan.apache.org <priv...@xalan.apache.org> Subject: Re: [VOTE][RESULT] Release Apache XalanJ 2.7.3 based on RC10 Sure, my point is that we have to publish twice, at least that's what we have to do over at Apache Commons: once for MC and once for CDN (was mirrors). Gary On Sat, Apr 1, 2023, 14:41 Milamber <milam...@apache.org<mailto:milam...@apache.org>> wrote: Hi, Please note that since 2021 (august), ASF stop usage of mirror system, now use CDN so release are immediately available after publising https://www.apache.org/mirrors https://apache.org/history/mirror-history.html On repository.a.o, when the jar files are promote for release, they become available on MC. Help for the process: https://infra.apache.org/publishing-maven-artifacts.html Milamber On 01/04/2023 17:47, Vladimir Sitnikov wrote: > It takes up to day for the mirrors and MC to sync up, assuming > repository.apache.org<http://repository.apache.org> was also used to stage > the release. I do not see Xalan on repository.apache.org<http://repository.apache.org>, and I see no traces of staged artifacts in the vote emails, so it does not sound like "mirrors sync up issue". It looks like the same thing happened for Xalan 2.7.2. It was not published to Central either https://issues.apache.org/jira/browse/XALANJ-2585 Could you please double-check if the release has been pushed to Central? Vladimir
