From: Joel Brobecker <brobecker@adacore.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sourceware.org
Subject: Re: DELAYED: GDB 6.7 branch creation scheduled June 25th
Date: Fri, 22 Jun 2007 16:16:00 -0000 [thread overview]
Message-ID: <20070622161752.GL18706@adacore.com> (raw)
In-Reply-To: <18043.30976.871935.736190@kahikatea.snap.net.nz>
> The next enhancement can always wait for the next release but if
> there's a bug that needs fixing, that needs to be done before the
> release.
Yes, of course.
> If you're saying branch and then fix before the release, there doesn't
> seem much point in testing until all the fixes are in. So where's the
> gain in branching early?
I disagree with the assumption that we are branching "early". We are
branching, because we need to branch to make a release. If the fix
for the bug doesn't make it before the branch is done, then we'll
just port the fix to the branch. If during testing we discover that
there is a significant issue, then we just delay the release.
--
Joel
next prev parent reply other threads:[~2007-06-22 16:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 6:18 GDB 6.7 branch creation scheduled June 10th Joel Brobecker
2007-06-08 6:39 ` Nick Roberts
2007-06-11 1:23 ` Daniel Jacobowitz
2007-06-14 18:54 ` Thiago Jung Bauermann
2007-06-14 18:58 ` Daniel Jacobowitz
2007-06-14 23:42 ` Joseph S. Myers
2007-06-21 18:13 ` DELAYED: GDB 6.7 branch creation scheduled June 25th Joel Brobecker
2007-06-21 18:22 ` H. J. Lu
2007-06-21 21:47 ` Nick Roberts
2007-06-22 1:39 ` Joel Brobecker
2007-06-22 7:23 ` Nick Roberts
2007-06-22 16:16 ` Joel Brobecker [this message]
2007-06-23 0:08 ` Nick Roberts
2007-06-23 0:34 ` Joel Brobecker
2007-06-23 0:58 ` Nick Roberts
2007-06-23 1:22 ` Joel Brobecker
2007-06-23 1:43 ` Nick Roberts
2007-06-23 4:44 ` Joel Brobecker
2007-06-24 0:44 ` Nick Roberts
2007-06-24 1:57 ` Daniel Jacobowitz
2007-06-25 23:54 ` Joel Brobecker
2007-06-26 19:00 ` Joel Brobecker
2007-06-26 19:15 ` Markus Deuling
2007-06-23 12:33 ` Daniel Jacobowitz
2007-06-22 20:14 ` Stan Shebs
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=20070622161752.GL18706@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--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