Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: DELAYED: GDB 6.7 branch creation scheduled June 25th
Date: Sat, 23 Jun 2007 00:58:00 -0000	[thread overview]
Message-ID: <18044.28720.838572.299857@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070623003622.GP18706@adacore.com>

 > > You've not really answered my question but the prerogative is yours, of
 > > course.
 > 
 > Can you ask your question again? I probably didn't understand what
 > you were asking.

It's just the one that I left in the the message "So where's the gain in
branching early?" but perhaps Stan Shebs answered it.

 > > Once the branch is made, I might miss the announcement for the
 > > imminent release, so I would only ask that the bug I have reported:
 > 
 > As of now, the release is scheduled one month after branching.
 > 
 > > http://sourceware.org/ml/gdb/2007-06/msg00022.html
 > > 
 > > is indeed fixed before the release.
 > 
 > You have to understand that this can not be guarantied by me.

You're the release manager so presumably you can insist on certain things
being done before a release is made.

 >                                                                I could
 > be underestimating the severity of the problem, but this issue hardly
 > seems blocking. 

It breaks existing use of Gdb in Emacs 22.1.

 >                  If you or anyone has a plan for fixing this issue
 > and promises to propose a patch within a reasonable timeframe (let's
 > say 2 weeks), then we can consider delaying the release a bit.

My plan would be just revert the change and I think Jan Kratochvil has agreed
with this.  AFAICS there's no reason why this would delay the release.

 > Otherwise, I think we should proceed, and just have this particular
 > issue documented as a known problem.

It's not just a bug but a regression.  I don't think breaking a feature
and then documenting it as a known problem is really an acceptable policy.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-06-23  0:58 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
2007-06-23  0:08           ` Nick Roberts
2007-06-23  0:34             ` Joel Brobecker
2007-06-23  0:58               ` Nick Roberts [this message]
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=18044.28720.838572.299857@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=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