On 19 January 2014 12:49, Gary Gregory <[email protected]> wrote: > Next problem: the VOTE passed, so I am releasing. > > C:\temp\rc\release-httpclient-4.3.2>gradlew -q promoteRC > Promoting HttpClient 4.3.2 RC1 to official release > Copying > https://svn.apache.org/repos/asf/httpcomponents/httpclient/tags/4.3.2-RC1to > https://svn.apache.org/repos/asf/httpcomponents/httpclient/tags/4.3.2 > > Good. Next, Logon on to Nexus, while the Wiki says to "Promote", that > option was disabled for me and all previous Commons release I worked on > used "Release" to release. So I picked that. > > Next is where I ran into: > > C:\temp\rc\release-httpclient-4.3.2>gradlew -q promoteDist > > FAILURE: Build failed with an exception. > > * Where: > Build file 'C:\temp\rc\release-httpclient-4.3.2\build.gradle' line: 605 > > * What went wrong: > Execution failed for task ':promoteDist'. >> org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: CHECKOUT > of > '/repos/dist/!svn/ver/4107/release/release%5Chttpcomponents/release%5Chttpcomponents%5Chttpclient': > 4 > 03 Forbidden (https://dist.apache.org) > > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. > > > Is this a karma problem or a process issue?
Karma. By default only PMC members have write access to the release tree. [Not sure why infra have this restrictive default] IIRC, Commons voted recently to change this to all Commons committers and asked Infra to change the auth. > Thank you, > Gary > > > > On Sat, Dec 28, 2013 at 6:56 AM, Oleg Kalnichevski <[email protected]> wrote: > >> Folks, >> >> I finally managed to put together a complete release process guide based >> on release automation tools I have been working on for the past 6 months >> [1]. >> >> The release tools should now simplify the most tedious and error-prone >> manual operations involved in a release. >> >> I actually managed to run the entire HttpCore 4.3.1 release process >> using the release tools only. >> >> Would anyone want to volunteer to be a release manager for HttpClient >> 4.3.2 and help me polish the scripts and the process guide? >> >> One would still need a fully functional Maven setup including GPG >> integration for artifact signing (as before), but otherwise the release >> process should no longer require any special tools beyond an IDE and a >> browser. Even a SVN client is not required. >> >> Oleg >> >> [1] http://wiki.apache.org/HttpComponents/HttpComponentsReleaseProcess >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second > Edition<http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
