-1

This is still wrong. The tag should be in the format VERSION-RC#. In this
case 2.0-rc1-rc2 (VERSION=2.0-rc1 and RC#=rc2). That's what we VOTE on, the
tag 2.0-rc1-rc#.

We are voting to release 2.0-rc1. The first try, 2.0-rc1-rc1, failed; now
we're on to the second: 2.0-rc1-rc2.

There must be a record of the code for the first attempt as an SVN tag,
which I see in SVN, good.

There currently is a 2.0-rc1 tag in SVN which should NOT exist until after
the VOTE for a given RC passes.

Gary

---------- Forwarded message ----------
From: <nickwilli...@apache.org>
Date: Sun, Feb 9, 2014 at 2:03 PM
Subject: svn commit: r1566354 - /logging/log4j/log4j2/tags/log4j-2.0-rc1/
To: comm...@logging.apache.org


Author: nickwilliams
Date: Sun Feb  9 19:03:23 2014
New Revision: 1566354

URL: http://svn.apache.org/r1566354
Log:
[maven-release-plugin]  copy for tag log4j-2.0-rc1

Added:
    logging/log4j/log4j2/tags/log4j-2.0-rc1/
      - copied from r1566353, logging/log4j/log4j2/trunk/




-- 
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

Reply via email to