From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: 21.2.90 pretest, 21.3, 21.4...
Date: Wed, 6 Nov 2002 08:13:33 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1021106080025.960B-100000@is> (raw)
In-Reply-To: <20021105213749.5845.LEKTU@terra.es>
On Tue, 5 Nov 2002, Juanma Barranquero wrote:
> > I explained elsewhere in this thread that mundane practical problems
> > caused this delay, in addition to real issues. I'm sorry that I was
> > part of the reasons for the delay, but I do have a life.
>
> If I´ve made it sound like I was looking for a culprit or disregarding
> in any way yours or anyone´s contribution or (sometimes huge) amount of
> work in this project, I´m really sorry. It´s not so.
It's true that I sometimes take offense where others don't, but in this
case, you have nothing to apologize for: your wording didn't come
anywhere near any disregard.
I simply wanted to explain why the delay happened. I truly _am_ sorry
that my personal life interfered.
> > I'm sure everyone knows that the way to speed up things is to
> > volunteer to make them happen.
>
> Yes, of course. But sometimes it´s not clear what can you volunteer for.
There are a few mundane tasks involved in a pretest: making the tarballs
and xdelta's, testing and uploading them, tracking the reports by
pretesters (like on which systems they built successfully, what
outstanding bugs are still unsolved, etc.). When there's a major
modification in the manuals, there's typically a need to record what
pages were reviewed and how many times, to ensure coverage. Etc., etc.
> I alredy fix bugs I think I know how to fix, for example.
If we want more frequent releases from the stable branch, bugs on the
branch should get priority, or at least there should be enough people
working on them to ensure they are fixed almost immediately.
Ideally, there should be a new pretest once a week. We are still very
far from that goal, I think; anything that helps us move toward that is a
welcome change.
next prev parent reply other threads:[~2002-11-06 6:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 16:16 21.2.90 pretest, 21.3, 21.4 Juanma Barranquero
2002-11-04 18:31 ` Stefan Monnier
2002-11-05 6:05 ` Eli Zaretskii
2002-11-05 7:02 ` Karl Eichwalder
2002-11-05 8:02 ` Juanma Barranquero
2002-11-05 18:40 ` Eli Zaretskii
2002-11-05 20:44 ` Karl Eichwalder
2002-11-06 6:29 ` Eli Zaretskii
2002-11-06 6:58 ` Karl Eichwalder
2002-11-06 14:18 ` Eli Zaretskii
2002-11-08 10:32 ` Kai Großjohann
2002-11-07 15:07 ` Richard Stallman
2002-11-05 8:02 ` Juanma Barranquero
2002-11-05 18:56 ` Eli Zaretskii
2002-11-05 12:02 ` Kai Großjohann
2002-11-05 19:00 ` Eli Zaretskii
2002-11-05 20:50 ` Stefan Monnier
2002-11-06 6:33 ` Eli Zaretskii
2002-11-06 12:40 ` Kim F. Storm
2002-11-06 12:55 ` Juanma Barranquero
2002-11-06 14:25 ` Eli Zaretskii
2002-11-06 14:49 ` Juanma Barranquero
2002-11-06 14:51 ` Miles Bader
2002-11-07 22:02 ` Francesco Potorti`
2002-11-07 8:08 ` (no subject) Kenichi Handa
2002-11-08 12:06 ` Richard Stallman
2002-11-07 22:00 ` 21.2.90 pretest, 21.3, 21.4 Francesco Potorti`
2002-11-09 11:54 ` Richard Stallman
2002-11-06 7:28 ` Kai Großjohann
2002-11-06 14:19 ` Eli Zaretskii
2002-11-06 7:49 ` Juanma Barranquero
2002-11-05 18:39 ` Stefan Monnier
2002-11-05 19:17 ` Eli Zaretskii
2002-11-05 20:37 ` Stefan Monnier
2002-11-06 6:00 ` Eli Zaretskii
2002-11-05 5:58 ` Eli Zaretskii
2002-11-05 7:56 ` Juanma Barranquero
2002-11-05 18:54 ` Eli Zaretskii
2002-11-05 20:40 ` Juanma Barranquero
2002-11-06 6:13 ` Eli Zaretskii [this message]
2002-11-06 4:49 ` Richard Stallman
2002-11-06 8:25 ` Juanma Barranquero
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 15:58 jasonr
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=Pine.SUN.3.91.1021106080025.960B-100000@is \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.