Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: Time for a new release?
Date: Wed, 15 Mar 2006 16:16:00 -0000	[thread overview]
Message-ID: <20060315043747.GA695@adacore.com> (raw)

Hello,

It's been almost 4 months since the last release (6.4). I was
unfortunately too busy lately to follow closely the GDB development.
I looked at the NEWS file, and see a few interesting thing there.
New commands, improved windows host support, etc.

Perhaps it is time to think about a new release? I'm thinking about
the following timeline:

        Branch: Apr 3rd
        Pre-release: Apr 5th
        Release: Apr 19th

Basically, a first pre-release a couple of days after branching.
And then the first release if all goes well two weeks after, to
give us some time to flush any issue we might find.

Also, do we want to distribute GDB with -Werror enabled? It's fair
to have us build GDB with -Werror, but I would feel more comfortable
distributing something that's easier to compiler for the end user.
I think this will avoid some traffic from users who don't know what
to do with the fatal warnings.

Thoughts?

-- 
Joel


             reply	other threads:[~2006-03-15  4:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 16:16 Joel Brobecker [this message]
2006-03-15 17:19 ` Christopher Faylor
2006-03-18  1:31   ` Daniel Jacobowitz

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=20060315043747.GA695@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.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