From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20242 invoked by alias); 9 Jul 2007 10:19:06 -0000 Received: (qmail 20234 invoked by uid 22791); 9 Jul 2007 10:19:06 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 09 Jul 2007 10:19:03 +0000 Received: from kahikatea.snap.net.nz (99.63.255.123.dynamic.snap.net.nz [123.255.63.99]) by viper.snap.net.nz (Postfix) with ESMTP id 06C363D8B83 for ; Mon, 9 Jul 2007 22:18:59 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 746C98FBF6; Mon, 9 Jul 2007 22:18:53 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18066.2956.730647.124877@kahikatea.snap.net.nz> Date: Mon, 09 Jul 2007 10:19:00 -0000 To: gdb@sources.redhat.com Subject: GDB version numbering X-Mailer: VM 7.19 under Emacs 22.1.50.3 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-07/txt/msg00061.txt.bz2 This is just a suggestion for a scheme for numbering GDB releases. Joel has suggested (I think) that the version after next is called 7.0. Major number changes, naturally, are generally reserved for major changes. However, as GDB usually releases fairly regularly, at about six monthly intervals, the scale of the changes tend to be pretty constant. So how about making the _next_ release 7.0 (or 7.1) and subsequent releases as: 2008 8.0 8.1 2009 9.0 9.1 2010 10.0 10.1 etc? Ubuntu do something like this. It would mean that infrequent users would start to realise how old their versions were and, hopefully, result in fewer out of date bug reports. -- Nick http://www.inet.net.nz/~nickrob