>>  >  Who can delete this tag please?
>>
>> Try using https: instead of http:

*arg* yes of course

> But why not try creating tag RC2 first, we vote on that, and if it
> succeeds we rename RC2 as the GA release tag?

cause the files which are created by maven during release process do
also contain -RC2 when deploying to staging area. I would have to
check out and rerun the procedure with the "normal" name. I can do
that of course, but the build isn't the same on which we voted. If
that isn't a problem we can do so.

cheers,
christian


>
>>  >  Thanks,
>>  >
>>  > Christian
>>  >
>>  >
>>  >  On Wed, May 13, 2009 at 7:09 AM, Christian Grobmeier
>>  >  <grobme...@gmail.com> wrote:
>>  >  > On Tue, May 12, 2009 at 7:41 PM, Dan Fabulich <d...@fabulich.com> 
>> wrote:
>>  >  >> When I ran it, the release plugin prompted me for the tag name to 
>> create.
>>  >  >> Rather than accept defaults, I manually typed in the appropriate tag 
>> name.
>>  >  >
>>  >  > OK, will try the same now, but at dbutils its only one tag availabe
>>  >  > even if you did some moe rcs:
>>  >  > http://svn.apache.org/viewvc/commons/proper/dbutils/tags/
>>  >  >
>>  >  > Did you delete the old tags afterwards?
>>  >  >
>>  >  > Christian
>>  >  >
>>  >  >>
>>  >  >> -Dan
>>  >  >>
>>  >  >> Christian Grobmeier wrote:
>>  >  >>
>>  >  >>> Hi,
>>  >  >>> currently the
>>  >  >>> mvn -Prc release:perform
>>  >  >>>
>>  >  >>> creates a tag with the release name instead of f.e.
>>  >  >>> commons-compress-1_0-RC1.
>>  >  >>>
>>  >  >>> 1) Do I have to remove the tag commons-compress-1_0 manually when
>>  >  >>> doing a second release candidate? Just want to make sure, don't want
>>  >  >>> to break the rules.
>>  >  >>>
>>  >  >>> 2) Is it really good to have a tag named like this instead with a
>>  >  >>> suffix RC1 or whatever?
>>  >  >>>
>>  >  >>> And yes, I will update:
>>  >  >>> http://wiki.apache.org/commons/CreatingReleases
>>  >  >>> with your answers :-)
>>  >  >>>
>>  >  >>> Best,
>>  >  >>> Christian
>>  >  >>>
>>  >  >>> ---------------------------------------------------------------------
>>  >  >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>  >  >>> For additional commands, e-mail: dev-h...@commons.apache.org
>>  >  >>>
>>  >  >>>
>>  >  >>
>>  >  >>
>>  >  >> ---------------------------------------------------------------------
>>  >  >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>  >  >> For additional commands, e-mail: dev-h...@commons.apache.org
>>  >  >>
>>  >  >>
>>  >  >
>>  >
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to