Please delete the tag
https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1/
; it should not exist since the software is not released.

Personally, I'd like to see a clean VOTE email at the very least with all
the bits in place in the message instead of reading through this whole
thread again.

If we also need another RC to pick up loose ends, then go ahead. This
thread is so old by now (in VOTE 'years') and there are so many replies
that I'd rather have a clean start (new VOTE and new RC.) but that's just
me.

Gary

On Mon, Nov 20, 2017 at 1:15 AM, Romain Manni-Bucau <[email protected]>
wrote:

> Guys,
>
> do we have a real blocker on the release? Being said having the RC or
> not now is pointless since the tag is there, are we waiting for
> anything particular? Happy to drop the RC if it brings more confusion
> than it helps.
>
> Romain Manni-Bucau
> @rmannibucau |  Blog | Old Blog | Github | LinkedIn
>
>
> 2017-11-11 16:05 GMT+01:00 Thomas Vandahl <[email protected]>:
> > On 06.11.17 21:11, Romain Manni-Bucau wrote:
> >> created http://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> commons-jcs-2.2.1-RC2/
> >> (rev 1814438)
> >
> > Thanks, Romain. However, the POM file in this RC tag contains now
> >
> > --8<--
> > <scm>
> >   <connection>
> >
> > scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/
> tags/commons-jcs-2.2.1
> >   </connection>
> >   <developerConnection>
> >
> > scm:svn:https://svn.apache.org/repos/asf/commons/proper/
> jcs/tags/commons-jcs-2.2.1
> >   </developerConnection>
> >   <url>
> >     http://svn.apache.org/viewvc/commons/proper/jcs/tags/
> commons-jcs-2.2.1
> >   </url>
> > </scm>
> > --8<--
> >
> > See my point? If you created the RC tag first and then copied, the
> > scm-entries would still point to the RC tag. In this case, it's the
> > other way round. It is difficult for me to see why this is believed to
> > make sense. I'd prefer to match tag name and file content.
> >
> > Bye, Thomas
> >
> > ---------------------------------------------------------------------
> > 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]
>
>

Reply via email to