This vote has failed to pass and is now closed. Bill-
On Tue, Jun 4, 2013 at 11:33 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > On Mon, Jun 3, 2013 at 9:25 PM, William Speirs <wspe...@apache.org> wrote: > >> I would like to release commons-dbutils 1.6 >> >> commons-dbutils 1.6 RC1 is available for review here: >> http://people.apache.org/~wspeirs/commons-dbutils-1.6-RC1/ (svn >> revision r1489259) >> >> Details of changes since 1.5 are in the release notes: >> http://people.apache.org/~wspeirs/commons-dbutils-1.6-RC1/RELEASE-NOTES.txt >> >> The tag is here: >> http://svn.apache.org/viewvc/commons/proper/dbutils/tags/DBUTILS_1_6_RC1/ >> >> Site: >> http://people.apache.org/~wspeirs/commons-dbutils-1.6-RC1/site/apidocs/ >> > > You should post the whole site, not just the Javadoc. We can then look at > all the reports. > > >> >> Votes, please. This vote will close in 72 hours >> >> [ ] +1 Release these artifacts >> [ ] +0 OK, but... >> [ ] -0 OK, but really should fix... >> [ ] -1 I oppose this release because... >> >> For what it's worth, I expect this RC to fail as I feel confident I >> did something wrong in the release process. The steps I followed I >> documented here: http://people.apache.org/~wspeirs/release_steps.html >> > > There is also https://wiki.apache.org/commons/UsingNexus > > >> >> If someone with experience release versions of commons software could >> walk me through how to do this properly I'd greatly appreciate it. I'd >> even be willing to update the documentation found here: >> http://commons.apache.org/releases/prepare.html >> >> For me, and maybe I'm alone on this, I simply find all of the bits and >> pieces that go into a release confusing and complicated: run this >> maven command, then copy these files to your home directory, then do >> something with Nexus (not even sure what that is), then delete those >> files from Nexus because it uploaded too much, then God forbid you >> want to change something after it was tagged. Why can't we have a few >> manual steps (make changes to code, change version in pom, done) and >> then a script that will generate the RC (doing all the copying and >> building, etc) and another to actually package and push the final >> release? I realize my contributions to commons are minimal, but I >> could see myself doing more if cutting RCs and pushing final releases >> were easier. Thoughts? Am I alone on this? >> > > Our release process sucks, there is no doubt about that. The only thing we > can do within the current process is improve the documentation and keep it > up to date. > > I'm sure I'm not the only one who would enjoy a less error-prone process. > > Gary > > >> >> Thanks! >> >> Bill- >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > 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: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
