On Apr 5, 2012, at 9:03 AM, Romain Manni-Bucau wrote: > for the 7.0.27: can't we simply deploy it manually to apache nexus?
We could manually sign all the binaries and manually deploy the binaries and the signatures and md5 files, sure. We'd still need to vote on them, though. -David > 2012/4/5 David Blevins <[email protected]> > >> >> On Apr 5, 2012, at 4:12 AM, Romain Manni-Bucau wrote: >> >>> it is already on repo1 and we only have to deploy the zip manually as we >>> did for 7.0.21. >>> >>> i really would like the 7.0.27 since some websocket work is included and >> is >>> a great improvement! >> >> We were deploying them into svn and listing svn as a repo. Infra asked us >> to find a better way as keeping binaries in svn is not really optimal. >> >> Getting them deployed as part of the Tomcat release process is the ideal >> approach and something I brought up on dev@tomcat. At this point, having >> a patch in hand is probably what is need to continue that discussion. >> Seems this is what we need to update: >> >> >> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk/res/maven/mvn-pub.xml >> >> >> As 7.0.27 is actually already published and completely finished, we >> probably just need to figure out a workaround for this build. Perhaps a >> tiny little maven project we can release like a regular release. >> >> >> -David >> >>> >>> 2012/4/5 Neale Rudd <[email protected]> >>> >>>> Compared to 7.0.21, I'd much prefer it on 7.0.26 or 27 if the release >>>> dates coincide. >>>> >>>> Today on Twitter: >>>> RT @TheApacheTomcat: 7.0.27 release vote passed. Release mechanics in >>>> progress. >>>> >>>> >> >>
