Perhaps adapt the release.sh to generate correct tags?

We should investigate using the maven release plugin, as it appears to
be improved. We should also look into upgrading our Apache parent, as
they have done a lot of stuff to make staging a release much more
easier, and deploying to the maven repo consistent, without removing
meta data from older releases...

Martijn

On Tue, Jun 2, 2009 at 10:25 PM, Jeremy Thomerson
<[email protected]> wrote:
> Thanks!  That's the part I didn't have time to work on last night.  I
> applied your commands and we should now have all of the proper tags.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Tue, Jun 2, 2009 at 2:21 PM, Max Bowsher <[email protected]> wrote:
>> Jeremy Thomerson wrote:
>>> Sorry, I had them still in my personal folder.  I have moved the
>>> release tags (for rc3 / rc4) to the releases folder.  However, I must
>>> not have cut a tag at the beginning of the rc4 release cycle - so I'm
>>> not sure what should go into the tags folder.
>>
>> Subversion to the rescue....
>> ------------------------------------------------------------------------
>> r771517 | jrthomerson | 2009-05-05 02:16:31 +0100 (Tue, 05 May 2009) | 1
>> line
>> Changed paths:
>>   A /wicket/sandbox/jthomerson/1.4-rc4 (from /wicket/trunk:771516)
>>
>> creating 1.4-rc4 tag pre-release
>> ------------------------------------------------------------------------
>>
>> Looks like you created your sandbox but supplied an erroneous commit
>> message.
>>
>> So, the relevant tag, to match the tagging policy exhibited in previous
>> wicket releases, would be:
>>
>> svn cp http://svn.apache.org/repos/asf/wicket/tr...@771516 \
>>  http://svn.apache.org/repos/asf/wicket/tags/wicket-1.4-rc4
>>
>>
>>
>>
>> A second issue concerning the tags: there currently exists BOTH a
>> "/tags/wicket-1.4-rc3" AND a "/tags/1.4-rc3" with DIFFERENT content. The
>> "/tags/wicket-1.4-rc3" one matches the way previous releases seem to be
>> tagged (trunk content, before pom.xml manipulation for release) whilst
>> the "/tags/1.4-rc3" one is equal to the content of
>> "/releases/wicket-1.4-rc3".
>>
>> I think "/tags/1.4-rc3" can simply be deleted.
>>
>>
>> Max.
>>
>>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

Reply via email to