From: Daniel Jacobowitz <drow@mvista.com>
To: Zaretskii Eli <ezaretski@elta.co.il>
Cc: Daniel Berlin <dberlin@dberlin.org>,
Elena Zannoni <ezannoni@redhat.com>,
Andrew Cagney <ac131313@redhat.com>,
gdb@sources.redhat.com
Subject: Re: [maint] The GDB maintenance process
Date: Thu, 20 Feb 2003 14:58:00 -0000 [thread overview]
Message-ID: <20030220145817.GA28816@nevyn.them.org> (raw)
In-Reply-To: <4D19136444628A40840EFE8C5AE04147017A44@ELTIMAIL1.elta.co.il>
On Thu, Feb 20, 2003 at 08:55:21AM +0200, Zaretskii Eli wrote:
>
> This message was scanned for viruses and other malicious code by PrivaWall.
>
>
> This mail was sent from ELTA SYS LTD.
>
>
> > From: Daniel Berlin [mailto:dberlin@dberlin.org]
> > Sent: Wednesday, February 19, 2003 3:24 PM
> >
> > > I guess I just don't see this to be as much of a problem as others
> do.
> > > For one thing, with the higher entropy level, more development
> actually
> > > happens.
> > Bingo.
> > I don't think we should stall development (and in the
> > extreme, even if
> > it means we can't make quality releases any day of the year) because
> > mistakes occasionally happen in patches, or because not every
> > maintainer in existence has said something about a patch. That's a
> > recipe for no progress.
>
> For some definition of ``progress''.
>
> Who said that adding code at a faster rate at the price of having more
> bugs is more ``progress'' than what we have now? There are people out
> there who need GDB to actually do something _useful_, not just to debug
> and/or develop GDB itself, you know. What about frustration of those
> GDB users when their favorite feature is broken by some
> committed-before-review patch that adds a hot new feature? Does that
> ever count?
I wouldn't have suggested this if I really thought that would happen.
> Does anyone remember that latest GCC releases are practically unusable
> for any production-quality work due to bugs? Does anyone even care?
And for the record, while I'd say that was true for 3.0, it was _not_
true for 3.1 or 3.2 or 3.2.1/3.2.2, which I consider production quality
compilers; and it won't be true for 3.3 either.
> Of course, if contributors are frustrated by the slow review rate, let's
> try to improve that (see my other mail). But let's not obscure our view
> of the problem by discussing abstract issues of ``progress''. An
> official release every 3 months is more than enough progress for my
> taste.
Not if there's nothing much new in it. Which is a bit of an
exaggeration, before anyone calls me on it - but still pretty well
expresses my point.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-20 14:58 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 20:11 Zaretskii Eli
2003-02-20 14:58 ` Daniel Jacobowitz [this message]
2003-02-20 15:56 ` Andrew Cagney
2003-02-20 16:39 ` Andrew Cagney
2003-02-20 15:16 ` Daniel Berlin
2003-02-20 16:19 ` Andrew Cagney
2003-02-20 16:24 ` Daniel Berlin
2003-02-20 16:31 ` Daniel Berlin
2003-02-20 17:13 ` Daniel Berlin
2003-02-22 23:25 ` Eli Zaretskii
2003-02-23 1:57 ` Daniel Berlin
2003-02-23 19:23 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 5:29 Michael Elizabeth Chastain
2003-02-20 20:11 Zaretskii Eli
2003-02-18 6:08 Zaretskii Eli
2003-02-17 18:07 Daniel Jacobowitz
[not found] ` <drow@mvista.com>
2003-02-17 18:58 ` Kevin Buettner
2003-02-17 21:01 ` Elena Zannoni
2003-02-19 1:49 ` Daniel Jacobowitz
2003-02-19 2:26 ` Joel Brobecker
2003-02-19 15:43 ` Andrew Cagney
2003-02-19 16:29 ` Daniel Jacobowitz
2003-02-19 22:04 ` Andrew Cagney
2003-02-19 13:24 ` Daniel Berlin
2003-02-19 15:51 ` Andrew Cagney
2003-02-19 14:50 ` Andrew Cagney
2003-02-19 17:33 ` David Carlton
2003-02-19 17:57 ` Kevin Buettner
2003-02-19 18:56 ` Andrew Cagney
2003-02-19 20:39 ` Christopher Faylor
2003-02-19 23:17 ` Jason Molenda
2003-02-20 1:53 ` Christopher Faylor
2003-02-19 19:35 ` David Carlton
2003-02-20 18:32 ` Richard Earnshaw
2003-02-22 0:53 ` Andrew Cagney
2003-02-19 15:12 ` Andrew Cagney
2003-02-19 15:21 ` Daniel Jacobowitz
2003-02-19 16:24 ` Andrew Cagney
2003-02-19 18:36 ` Christopher Faylor
2003-02-19 23:36 ` Jason Molenda
2003-02-19 23:52 ` Andrew Cagney
2003-02-19 23:59 ` Jason Molenda
2003-02-20 0:16 ` Elena Zannoni
2003-02-20 0:21 ` Andrew Cagney
2003-02-18 2:39 ` Andrew Cagney
2003-02-18 4:28 ` Andrew Cagney
2003-02-19 3:49 ` Jim Blandy
2003-02-19 16:14 ` Andrew Cagney
2003-02-19 16:31 ` Daniel Jacobowitz
2003-02-19 2:24 ` Jim Blandy
2003-02-19 16:33 ` Andrew Cagney
2003-02-19 22:24 ` Jim Blandy
2003-02-19 22:39 ` Christopher Faylor
2003-02-19 22:53 ` Andrew Cagney
2003-02-19 23:53 ` Elena Zannoni
2003-02-20 1:27 ` Andrew Cagney
2003-02-20 2:48 ` Andrew Cagney
2003-02-21 23:43 ` Andrew Cagney
2003-02-21 23:57 ` Andrew Cagney
2003-02-19 6:05 ` David Carlton
2003-02-23 23:26 ` Mark Kettenis
2003-02-24 7:18 ` Andrew Cagney
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=20030220145817.GA28816@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=dberlin@dberlin.org \
--cc=ezannoni@redhat.com \
--cc=ezaretski@elta.co.il \
--cc=gdb@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