Le mar. 31 mars 2020 à 16:47, Gary Gregory <[email protected]> a écrit :
>
> On Tue, Mar 31, 2020 at 10:39 AM Gilles Sadowski <[email protected]>
> wrote:
>
> > Le mar. 31 mars 2020 à 15:59, Gary Gregory <[email protected]> a
> > écrit :
> > >
> > > On Tue, Mar 31, 2020 at 8:27 AM Gilles Sadowski <[email protected]>
> > > wrote:
> > >
> > > > Le mar. 31 mars 2020 à 14:11, sebb <[email protected]> a écrit :
> > > > >
> > > > > On Mon, 30 Mar 2020 at 23:20, Gilles Sadowski <[email protected]>
> > > > wrote:
> > > > > >
> > > > > > Hi.
> > > > > >
> > > > > > Le lun. 30 mars 2020 à 23:37, Matt Juntunen
> > > > > > <[email protected]> a écrit :
> > > > > > >
> > > > > > > Thanks. I think I have the gpg key sorted now.
> > > > > > >
> > > > > > > I can probably start on RC2 tomorrow. It sounds like we've
> > agreed to
> > > > go with "1.0-beta1" for the release version so I'm wondering what to do
> > > > with the existing release branch (1.0-B1-release) and tag
> > > > (NUMBERS_1_0_B1_RC1). These should have probably been
> > 1.0-beta1-release and
> > > > NUMBERS_1_0_BETA1_RC1. Is it possible to drop those and recreate them
> > or
> > > > would it be better to leave the current branch and tag names as-is and
> > use
> > > > the NUMBER_1_0_BETA1_RCX tag pattern going forward?
> > > >
> > >
> > > IMO, the tagging should be:
> > >
> > > <component-id>-<release>[-RC#]
> > >
> > > So:
> > >
> > > commons-number-1.0-beta1-RC1
> > > commons-number-1.0-beta1
> > >
> >
> > For [Math] and [RNG] (and [Lang] until 3.10),
> > $ git tag --list
> > shows a format akin to
> > MATH_3_6_1_RC
> >
>
> I know and my opinion is that the format above is lame ;-)

I didn't particularly liked it either but I'm quite sure that it
wouldn't have sufficed for a change.

I'm fine with improving the (common?) convention.

Why not dropping the redundant reference to the component
and project, since they are in the repo's name?
And how about focusing on the tag's purpose by mentioning
it first?
Thus:
    rc1_v1.0-beta1

Gilles

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to