On Wed, Jun 29, 2011 at 11:49 AM, Phil Steitz <[email protected]> wrote: > On 6/29/11 8:58 AM, Simone Tripodi wrote: >> Hi all guys, >> I just realized that the tag[1] dir name is in the wrong pattern - I >> overlooked the fact that the release:plugin tagged with the default >> one :( >> Now the question is: is it fine just moving it with a 'svn move' or >> the RC has to be rebuilt from scratch? >> Many thanks in advance, have a nice day! > > As long as the contents of the tag correspond to what is in the RC, > you are OK. The important thing is that the tag name should include > "RC" in it so it is not mistaken for a final release tag, which > should be created after the VOTE succeeds.
*Created*, or renamed? Matt > > Phil >> Simo >> >> [1] >> https://svn.apache.org/repos/asf/commons/proper/digester/tags/commons-digester3-3.0/ >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >> >> >> On Tue, Jun 28, 2011 at 11:14 PM, Simone Tripodi >> <[email protected]> wrote: >>> Hi Dave, >>> very nice to meet you and thanks for reporting! >>> That should be non blocking, once the 3.0 release passed, the >>> 3.1-SNAPSHOT site will be re-deployed and will override wrong >>> link/deprecated and already fixed references! >>> Have a nice day! >>> Simo >>> >>> http://people.apache.org/~simonetripodi/ >>> http://www.99soft.org/ >>> >>> >>> >>> On Tue, Jun 28, 2011 at 9:55 PM, Dave Brosius <[email protected]> >>> wrote: >>>> Perhaps i am confused but it appears the source code links on the web >>>> site (http://commons.apache.org/digester/source-repository.html) are >>>> wrong,http://svn.apache.org/viewvc/commons/sandbox/digester3/trunk >>>> svn checkout >>>> http://svn.apache.org/repos/asf/commons/sandbox/digester3/trunk >>>> commons-digester3 Is this the right one -- it seems to worksvn checkout >>>> http://svn.apache.org/repos/asf/commons/proper/digester/trunk >>>> commons-digesterCould someone fix them, (or me, which ever is wrong?)dave >>>> ----- Original Message -----From: "Simone Tripodi" >>>> >;[email protected] >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
