On Tue, Jun 4, 2013 at 8:08 AM, Benedikt Ritter <brit...@apache.org> wrote:
> Hi Bill, > > > 2013/6/4 William Speirs <wspe...@apache.org> > > > My confusion, it says in those directions to remove the -SNAPSHOT from > the > > version. That's exactly what I did. So then I shouldn't submit that to > > trunk? I thought you were supposed to get everything setup in trunk then > > simply svn copy that to your tag. > > > > This is what we do at my company. Tags should never be changed. OTOH trunk > should always contain the latest (=SNAPSHOT) code. If trunk ever contains a > non SNAPSHOT version, the nightly build will push that version to the > snapshot repo. And that is definitively worse than changing a tag. > > > > > > If I were to start working on a python script that performed all of these > > steps, so they can be verified by the community, and then submit that > > alongside the source, would others find this helpful? > What steps exactly? I set the version back and forth with Maven and SVN (revert) for example. Our release process is ridiculously burdensome IMO, anything will help. Here is the stuff I did for Codec 1.8: commons-codec 1.8 set the release date in changes.xml mvn -Darguments=-Dgpg.passphrase=MyPwd -Dgpg.passphrase=MyPwd clean deploy -Prelease Download src.zip file and build. mvn versions:set -DnewVersion=1.8 -DgenerateBackupPoms=false mvn commons:download-page svn revert pom.xml svn commit -m"Release preparation for 1.8-RC4." svn update mvn versions:set -DnewVersion=1.8 -DgenerateBackupPoms=false Set version in default.properties svn copy . -m"Create commons-codec-1.8-RC4." https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4 svn revert pom.xml svn revert default.properties rd c:\temp\codec\RC /s/q && md c:\temp\codec\RC && cd c:\temp\codec\RC svn co https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4c:\temp\codec\RC mvn -Darguments=-Dgpg.passphrase=MyPwd -Dgpg.passphrase=MyPwd deploy -Prelease Close repo: https://repository.apache.org/index.html https://repository.apache.org/content/repositories/orgapachecommons-130/ mvn site DOES NOT WORK: mvn site:stage-deploy -DstagingDirectory=src/site -DstagingSiteURL=scp:// people.apache.org/x1/builds/commons/commons-codec/1.8/RC1 [INFO] maven.site.deploy.skip = true: Skipping site deployment Upload local site to my people page Email [VOTE] Release Commons Codec 1.8-RC4 [Take 3] Email [RESULT][VOTE] Release Commons Codec 1.8-RC4 [Take 3] ssh people.apache.org cd release rm * wget -r -l 1 -np -nH -nd -nv -e robots=off --wait 5 --no-check-certificate https://repository.apache.org/content/repositories/orgapachecommons-130/commons-codec/commons-codec/1.8/ go to repository.apache.org delete .tar.gz and .zip (and their asc files) chown :commons * chgrp commons * chmod g+w * svn mkdir -m "Creating initial directory structure for Commons Codec" https://dist.apache.org/repos/dist/dev/commons/codec svn mkdir -m "Creating initial directory structure for Commons Codec" https://dist.apache.org/repos/dist/dev/commons/codec/binaries svn mkdir -m "Creating initial directory structure for Commons Codec" https://dist.apache.org/repos/dist/dev/commons/codec/source cd C:\repo\svn\apache\dist\dev\commons\codec svn co https://dist.apache.org/repos/dist/dev/commons/codec . set repo_path=c:\temp\codec\rc\target set release_path=C:\repo\svn\apache\dist\dev\commons\codec In the file explorer, copy all the -bin and -src files to the release path in binaries and source. checkout https://dist.apache.org/repos/dist/release/commons/codec copy/add/commit 1.8 files update readme HTML files svn copy https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4 https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8 -m"Create 1.8 GA tag." Gary > > > > If this is possible it would be more than welcome, I guess... (I've never > done a RC) > > > > > > Thanks... > > > > Bill- > > On Jun 4, 2013 7:01 AM, "sebb" <seb...@gmail.com> wrote: > > > > > http://commons.apache.org/releases/prepare.html#Manual_Method > > > > > > On 4 June 2013 11:56, William Speirs <wspe...@apache.org> wrote: > > > > Is there documentation about this somewhere? What should I have done? > > > > > > > > Thanks... > > > > > > > > Bill- > > > > On Jun 4, 2013 5:02 AM, <s...@apache.org> wrote: > > > > > > > >> Author: sebb > > > >> Date: Tue Jun 4 09:02:02 2013 > > > >> New Revision: 1489347 > > > >> > > > >> URL: http://svn.apache.org/r1489347 > > > >> Log: > > > >> Only tags should use non-SNAPSHOT versions please > > > >> > > > >> Modified: > > > >> commons/proper/dbutils/trunk/pom.xml > > > >> > > > >> Modified: commons/proper/dbutils/trunk/pom.xml > > > >> URL: > > > >> > > > > > > http://svn.apache.org/viewvc/commons/proper/dbutils/trunk/pom.xml?rev=1489347&r1=1489346&r2=1489347&view=diff > > > >> > > > >> > > > > > > ============================================================================== > > > >> --- commons/proper/dbutils/trunk/pom.xml [utf-8] (original) > > > >> +++ commons/proper/dbutils/trunk/pom.xml [utf-8] Tue Jun 4 09:02:02 > > > 2013 > > > >> @@ -24,7 +24,7 @@ > > > >> <modelVersion>4.0.0</modelVersion> > > > >> <groupId>commons-dbutils</groupId> > > > >> <artifactId>commons-dbutils</artifactId> > > > >> - <version>1.6</version> > > > >> + <version>1.6-SNAPSHOT</version> > > > >> <name>Commons DbUtils</name> > > > >> > > > >> <inceptionYear>2002</inceptionYear> > > > >> > > > >> > > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter > -- 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
