On Dec 29, 2013, at 6:04 AM, Mark Thomas <ma...@apache.org> wrote: > On 14/11/2013 02:58, Jeremy Boynes wrote: >> I'd like to release Apache Standard Taglib 1.2.1. This is an update >> to the withdrawn 1.2.0, built with JDK 1.7.0_45 to address JavaDoc >> issues and incorporating feedback on the documentation. >> >> Maven Staging Repository: >> https://repository.apache.org/content/repositories/orgapachetomcat-132/ >> >> Source Distribution: >> https://repository.apache.org/content/repositories/orgapachetomcat-132/org/apache/taglibs/taglibs-standard/1.2.1/ >> >> SVN tag: >> https://svn.apache.org/repos/asf/tomcat/taglibs/standard/tags/taglibs-standard-1.2.1 >> @ r1541786 https://svn.apache.org/r1541786 >> >> KEYS: https://svn.apache.org/repos/asf/tomcat/trunk/KEYS >> >> The proposed 1.2.1 release is: [ ] Broken - do not release [X] OK - >> release as 1.2.1 > > My vote is conditional on the src tarball being made available via the > Apache Mirror system. I'd would have expected a link to > https://dist.apache.org/repos/dist/dev/tomcat/... included in the vote > thread.
With the build being Maven based, I followed the doc here: http://www.apache.org/dev/publishing-maven-artifacts.html and I did not see anything about publishing through both channels. I’ve uploaded a copy of the source release here: https://dist.apache.org/repos/dist/dev/tomcat/taglibs/taglibs-standard-1.2.1/ Is that what you had in mind? Do I just svn mv that to “release” when done? Thanks Jeremy
signature.asc
Description: Message signed with OpenPGP using GPGMail
