Karl, Done. The steps reflected my changes immediately on public page http://maven.apache.org/shared/ No more waiting one day for CMS job. Thanks.
The only question, for next time release, is what happened after I went through https://cms.apache.org/maven/publish 1. Did the publish take successful svn commit: svn commit -m "Apache Maven Shared Utils 0.8 Released" Authentication realm: <https://svn.apache.org:443> ASF Committers Username: tibordigana Password for 'tibordigana': ******** Sending index.apt Transmitting file data . Committed revision 1686696. 2. or it took the CMS "Staged" from yesterday when I modified the index.apt in browser Submitted and Staged. There's is document and video describing how to use CMS bookmark. I would say the SVN is more natural way for me, and CMS is what did not work for me however CMS told me that everything was successful. I was waiting 20 hours after the CI should process CMS changes which should normally take one day. What's wrong with the CMS? It looks like CMS is official and everybody says use it, but it looks like reality is different and we should commit in SVN like you described instead of using CMS in browser. Maybe CMS commits in SVN on the same in the background, but if it does then I can do the same in svn even better. Ideas? -- View this message in context: http://maven.40175.n5.nabble.com/RESULT-VOTE-Release-Apache-Maven-Shared-Utils-version-0-8-tp5838056p5838243.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
