Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: GDB 7.1 release planning...
Date: Fri, 08 Jan 2010 04:21:00 -0000	[thread overview]
Message-ID: <20100108042117.GK4623@adacore.com> (raw)

Hello,

Time flies. I didn't realize this, but the tentative date for creating
the GDB 7.1 branch was set to Jan 20th, so only 12 days away from now.
It might be a little tight (or not) depending on what we'd like to have
in this release.

Is there anything that would be blocking for the branch creation?
There is a Wiki page for the gdb-7.1 release:

    http://sourceware.org/gdb/wiki/GDB_7.1_Release

There's been one item for a while but it's about documentation,
which is not blocking for the branch (might already be done too).

Anything that would be highly desirable and would potentially
justify delaying the branch?

Thanks,
-- 
Joel


             reply	other threads:[~2010-01-08  4:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08  4:21 Joel Brobecker [this message]
2010-01-08  9:24 ` Tristan Gingold
2010-01-08 11:08   ` Joel Brobecker
2010-01-08 13:49 ` Jan Kratochvil
2010-01-08 18:44   ` Michael Snyder
2010-01-09  3:08   ` Joel Brobecker
2010-01-08 13:53 ` Daniel Jacobowitz
2010-01-08 16:14   ` Tom Tromey
2010-01-09  3:18     ` Joel Brobecker
2010-01-11 19:58       ` Tom Tromey
2010-01-14  4:54         ` Joel Brobecker
2010-01-08 19:28 ` Stan Shebs
2010-01-08 22:32   ` Pedro Alves
2010-01-08 23:46     ` Stan Shebs
2010-01-09  3:31       ` Joel Brobecker
2010-01-09 16:52         ` Marc Khouzam
2010-01-11  9:48           ` Joel Brobecker
2010-01-11 14:31           ` Pedro Alves
2010-01-11 14:36         ` Pedro Alves
2010-01-13 23:17 ` Michael Snyder
2010-01-14  3:30   ` Joel Brobecker

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=20100108042117.GK4623@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    /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