Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: Nick Roberts <nickrob@snap.net.nz>,
	Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB version numbering
Date: Tue, 10 Jul 2007 16:58:00 -0000	[thread overview]
Message-ID: <4693BACE.3030000@redhat.com> (raw)
In-Reply-To: <18066.47945.530232.677872@kahikatea.snap.net.nz>

Nick Roberts wrote:
>  > > 2008    8.0    8.1
>  > > 2009    9.0    9.1
>  > > 2010   10.0   10.1
>  > > etc?
>  > 
>  > Honestly, I don't think this bring any benefit at all. version 10.x
>  > is as cryptic as version 6.x. Perhaps if you had suggested that
>  > we use version 2008, 2009, etc. But even then I don't see any benefit.
>
> I don't see how it can be as cryptic.  I know Ubuntu 6.04 is about 15 months
> old.  Can you tell me offhand how old GDB 5.3 or GDB 4.18 is?  The benefit
> probably isn't great but then there is no expense either.
>
>   

The reason to bump the major version doesn't need to be technical and 
previously hasn't.  For instance, 5.x signified the freeing of GDB's CVS 
repo.  Here, similarly, we've got the GPLv3 change that while 
non-technical is a very major change for GDB;  something worth 
considering as a trigger for a major version number bump:

    GDB 7 is GPLv3+
    GDB 6 is GPLv2+

Andrew


>  > I prefer the current numbering scheme. We can keep a 6.x version number
>  > until we have something major happening. The last time, it was the
>  > transition to multi-arch I think. For 7.0, it looks like it will be
>  > python scripting support.
>
> It will surely be an impressive feat but AFAICS it's still just the work of one
> person.  The major number changes seem a little bit arbitrary and perhaps
> diminish the work of others who contribute towards a minor number change.
> It's not a big deal though, I was just brainstorming a bit.
>
>   


  reply	other threads:[~2007-07-10 16:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 10:19 Nick Roberts
2007-07-09 17:20 ` Joel Brobecker
2007-07-09 22:48   ` Nick Roberts
2007-07-10 16:58     ` Andrew Cagney [this message]
2007-07-10 19:23       ` Joel Brobecker
2007-07-10 19:33         ` Daniel Jacobowitz
2007-07-10 20:14           ` Eli Zaretskii
2007-07-10 19:42         ` Dave Korn
2007-07-10 20:17           ` Eli Zaretskii

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=4693BACE.3030000@redhat.com \
    --to=cagney@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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