From: Elena Zannoni <ezannoni@cygnus.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: jtc@redback.com, Michael Elizabeth Chastain <chastain@cygnus.com>,
ac131313@cygnus.com, gdb@sources.redhat.com
Subject: Re: CVS versions of gdb have same number as stable version.
Date: Fri, 16 Feb 2001 12:29:00 -0000 [thread overview]
Message-ID: <14989.36272.996420.519178@kwikemart.cygnus.com> (raw)
In-Reply-To: <1010216201646.ZM12268@ocotillo.lan>
Kevin Buettner writes:
> On Feb 16, 11:57am, J.T. Conklin wrote:
>
> > If I'm not misremembering the 5.0.XX convention (perhaps it's only
> > used for formal 5.1 test releases), I'd approve the change. I
> > strongly prefer that form to "-experimental". But I would prefer
> > input from others, cuz it seems somehow wrong to approve your own
> > proposal.
>
> I think that 5.0.XX makes sense for the branch that'll eventually be
> created for the 5.1 release. For the development sources, I think
> that Michael C's suggestion of "5.1-experimental" (or whatever it was)
> is preferable since it also clearly distinguishes between release
> candidates and the ongoing development on the trunk.
>
> Kevin
>
Let's look at the history:
1999-04-09 Jim Blandy <jimb@zwingli.cygnus.com>
* GDB 4.18 released.
* Makefile.in (VERSION): Bump to 4.18.1.
Mon Mar 2 17:04:25 1998 Jason Molenda (crash@bugshack.cygnus.com)
* Makefile (VERSION): Bump to 4.17.1.
Mon Apr 22 20:17:01 1996 Fred Fish <fnf@cygnus.com>
* Makefile.in (VERSION): Bump version number to 4.16.1.
* NEWS: Update for 4.16 release.
Wed Feb 28 15:50:12 1996 Fred Fish <fnf@cygnus.com>
* Makefile.in (VERSION): Bump version to 4.15.2 to establish
baseline for gdb 4.16 rerelease testing.
Wed Oct 11 17:25:59 1995 Fred Fish <fnf@rtl.cygnus.com>
* Makefile.in (VERSION): Bump version to 4.15.1
Tue Oct 10 15:26:39 1995 Fred Fish <fnf@cygnus.com>
* Makefile.in (VERSION): Version 4.15 released.
* README: Updated for version 4.15.
* NEWS: Updated for 4.15 release.
Etc. Etc.
I am in favour of 5.0.1, which is consistent with what we did in the
past.
Elena
next prev parent reply other threads:[~2001-02-16 12:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 11:29 Michael Elizabeth Chastain
2001-02-16 11:42 ` Andrew Cagney
2001-02-16 11:57 ` J.T. Conklin
2001-02-16 12:16 ` Kevin Buettner
2001-02-16 12:29 ` Elena Zannoni [this message]
2001-02-16 12:43 ` Kevin Buettner
2001-02-16 12:44 ` Andrew Cagney
2001-02-16 13:34 ` Stan Shebs
2001-02-16 14:30 ` Christopher Faylor
2001-02-17 10:51 ` Andrew Cagney
2001-03-21 15:59 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2001-06-12 14:46 Michael Elizabeth Chastain
2001-06-13 7:32 ` Andrew Cagney
2001-03-21 15:59 Michael Elizabeth Chastain
2001-02-16 12:21 Michael Elizabeth Chastain
2001-03-21 15:59 ` Andrew Cagney
2001-02-16 8:46 Michael Elizabeth Chastain
2001-02-16 9:54 ` Kevin Buettner
2001-02-16 11:02 ` J.T. Conklin
2001-02-16 12:10 ` Eli Zaretskii
2001-02-16 8:07 Michael Elizabeth Chastain
2001-02-16 8:39 ` Andrew Cagney
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` Fernando Nasser
2001-03-21 15:59 ` Fernando Nasser
2001-06-12 14:14 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14989.36272.996420.519178@kwikemart.cygnus.com \
--to=ezannoni@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=chastain@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=jtc@redback.com \
--cc=kevinb@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox