commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Date Sat, 09 Dec 2017 21:09:56 GMT
Hmmm, sorry Gary but I'm not sure how to read this answer.

Le 9 déc. 2017 20:04, "Gary Gregory" <garydgregory@gmail.com> a écrit :

I know releasing is a pain but folks do it all the time, this is what we
have released since the last board report:

→ *BCEL-6.1* was released on Sun Sep 17 2017
→ *BCEL-6.2* was released on Thu Dec 07 2017
→ *CODEC-1.11* was released on Thu Oct 19 2017
→ *COMPRESS-1.15* was released on Mon Oct 16 2017
→ *CONFIGURATION-2.2* was released on Wed Oct 11 2017
→ *DAEMON-1.1.0* was released on Tue Nov 21 2017
→ *IO-2.6* was released on Sat Oct 14 2017
→ *JELLY-1.0.1* was released on Sat Sep 23 2017
→ *LANG-3.7* was released on Tue Nov 07 2017
→ *POOL-2.4.3* was released on Fri Oct 27 2017
→ *VFS-2.2* was released on Thu Oct 05 2017

Personally, I do most steps manually instead of using the release plugin.
YMMV.

Gary

On Sat, Dec 9, 2017 at 9:04 AM, Romain Manni-Bucau <rmannibucau@gmail.com>
wrote:

> Last up guys, from what has been said there is no clean way to do a
> commons release (RC procedure *does not* work cause it does not enable
> to do a final release through a copy) so the original vote mail is
> probably the best compromise we can have today. Since the vote is a
> bit old now I ping a last time to try to get the needed binding votes
> and if we judge it must be cancelled/restarted I will just delete all
> the stagings next week (probably friday).
>
> Romain Manni-Bucau
> @rmannibucau |  Blog | Old Blog | Github | LinkedIn
>
>
> 2017-11-21 6:58 GMT+01:00 Romain Manni-Bucau <rmannibucau@gmail.com>:
> >
> >
> > Le 20 nov. 2017 19:44, "Gary Gregory" <garydgregory@gmail.com> a écrit :
> >
> > 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.
> >
> >
> > No, the RC should not exist. This one is the only correct one since it
is
> > aligned between version, name and source content. All other tag would be
> > wrong and unusable for a vote and there is no other way to handle it on
> svn
> > except a branch which is not what we want.
> >
> >
> >
> > 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 <
> rmannibucau@gmail.com>
> > 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 <tv@apache.org>:
> >> > 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: dev-unsubscribe@commons.apache.org
> >> > For additional commands, e-mail: dev-help@commons.apache.org
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message