unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo <sdl.web@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca,
	Angelo Graziosi <angelo.graziosi@alice.it>
Subject: Re: Bash scripts in black and white
Date: Sat, 15 May 2010 10:51:18 +0100	[thread overview]
Message-ID: <xbaibpchjxwp.fsf@cam.ac.uk> (raw)
In-Reply-To: 838w7lfzdo.fsf@gnu.org

On 2010-05-15 07:33 +0100, Eli Zaretskii wrote:
>> PS. Sometime one gets the idea that Emacs's developers do not test 
>> deeply (for example, with at least a clean bootstrap) their changes... 
>> This would explain why the bugs tracker is at #6193 :-)
>
> I won't recommend drawing any conclusions from just the number of the
> last filed bug.  Especially since the Emacs bug database is shared
> with other projects (e.g., Coreutils).  As another data point, the GNU
> Make's bug number approaches 30,000...
>
> More to the point: Emacs maintainers do test as deeply as practically
> possible for each one of them.  A bootstrap is a lengthy procedure for
> someone who has maybe an hour a day to work on Emacs.  We are grateful
> to all those who do have resources to bootstrap and test on other
> systems, and report results here.

I think users have much higher expectation of software quality these
days since there are far more good applications both commercial and
free. And frankly emacs is playing catch-up. The good quality part is
from decades of bug reports and fixes. Most recent additions are not due
to lack of exposure and due to lack of people care enough to report and
lack of people care enough to fix. What I know as truth is emacs may
hang more often than any applications on your system including the
webbrowser, which handles contents far more complex and it is making
emacs 'irrelevant' as time goes by. Let me cite one example here
http://code.google.com/p/latex-lab/.

I also think it would be very helpful for emacs to have a daily build
report on one of the main platforms. This will help developers use their
time more effectively. To the outside, any breakage will last not more
than one day. Such routine can be automated. I have seen it done by
individual user and I have no doubt it can be done in the GNU project.

Leo



  parent reply	other threads:[~2010-05-15  9:51 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13  9:16 Bash scripts in black and white Angelo Graziosi
2010-05-14 12:16 ` Thierry Volpiatto
2010-05-14 19:29 ` Stefan Monnier
2010-05-14 19:58   ` Thierry Volpiatto
2010-05-14 21:23   ` Angelo Graziosi
2010-05-14 22:40     ` Lennart Borgman
2010-05-15  5:30       ` joakim
2010-05-15 13:56       ` Stefan Monnier
2010-06-27 14:21         ` Christian Ohler
2010-05-15  6:33     ` Eli Zaretskii
2010-05-15  8:15       ` Angelo Graziosi
2010-05-15  9:12         ` Juanma Barranquero
2010-05-15  9:20           ` Angelo Graziosi
2010-05-15  9:34             ` Juanma Barranquero
2010-05-15 11:43               ` Angelo Graziosi
2010-05-15  9:51       ` Leo [this message]
2010-05-15 12:11         ` Eli Zaretskii
2010-05-15 12:49           ` martin rudalics
2010-05-15 13:05             ` Leo
2010-05-15 17:12               ` Romain Francoise
2010-05-16 18:38                 ` Ken Raeburn
2010-06-24 17:58                 ` Ted Zlatanov
2010-06-24 22:11                   ` Stefan Monnier
2010-06-25  5:18                     ` Thierry Volpiatto
2010-06-26 22:23                       ` Stefan Monnier
2010-06-27  5:09                         ` Thierry Volpiatto
2010-06-30 18:26                     ` buildbot setup (was: Bash scripts in black and white) Ted Zlatanov
2010-06-30 18:39                       ` Lennart Borgman
2010-06-30 19:06                         ` buildbot setup Ted Zlatanov
2010-06-30 21:34                           ` Lennart Borgman
2010-07-01 13:00                             ` Ted Zlatanov
2010-07-01 13:08                               ` Lennart Borgman
2010-07-01  1:43                       ` Stefan Monnier
2010-07-01  4:32                         ` Stephen J. Turnbull
2010-07-04 21:26                           ` Stefan Monnier
2010-07-04 22:56                             ` joakim
2010-05-15 10:36     ` Bash scripts in black and white Thierry Volpiatto
2010-05-17 19:45     ` Stephen Eilert

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xbaibpchjxwp.fsf@cam.ac.uk \
    --to=sdl.web@gmail.com \
    --cc=angelo.graziosi@alice.it \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).