From: "Drew Adams" <drew.adams@oracle.com>
To: "'Leo'" <sdl.web@gmail.com>, <emacs-devel@gnu.org>
Subject: RE: Next pretest, and branching plans
Date: Sat, 20 Feb 2010 08:52:50 -0800 [thread overview]
Message-ID: <136A0B1647B74A53A26506F872BECC6E@us.oracle.com> (raw)
In-Reply-To: <xbaizl34drgb.fsf@cam.ac.uk>
> > If pretest feedback from Windows users is at all useful or
> > important to you, then you might consider this a loss.
> > If not, just keep on rolling...
>
> Is a policy to provide a binary for windows? There's no binary for
> GNU/Linux, OSX and many others.
I cannot speak to what the "policy" is, or whether there even is a policy. I
make no claim about policy.
GNU Emacs does publish this, FWIW:
http://alpha.gnu.org/gnu/emacs/pretest/windows/.
The README there (from 2010/01/03) says, "This directory contains precompiled
distributions for GNU Emacs on Windows".
That is, GNU Emacs publishes a directory that has _only_ Windows binaries.
No, the README does not claim that the directory includes a binary of the latest
pretest. And it did not include a binary for the previous pretest (23.1.91)
either, until we reminded about it a few times and Jason found time to create
and post it (thank you).
But prior to that, AFAIK, it generally _has_ included pretest binaries.
I repeat: *IF* such feedback from Windows users is important to Emacs
development, then you might consider that not posting a binary will reduce
useful feedback.
Speaking for myself only, that will be the case. As an example, I recently spent
some time with Michael A. trying to debug and fix bug #5478, and we were forced
to test using the previous Windows pretest because the latest was not available.
With no pretest binaries at all, next time perhaps we will need to wait for a
binary of the next release. Or the bug might find someone who wants to not only
fix the bug but also build Emacs on Windows.
Perhaps more importantly, there will be fewer (far fewer, IMO) new bug reports
from Windows users for the latest code. Instead of a pretest, you will, in
effect, just wait until after the release to get such bug reports. The purpose
of the pretest will thus be defeated, except for those Windows pretesters who
are willing to build Emacs.
Speaking for myself again, I have submitted many bug reports for Emacs pretests,
including for the last one (23.1.91). I submitted none for 23.1.92, since there
was no binary. IF you think that bug reports during pretest can be helpful in
general, then this is a loss.
> But when I was using Windows, I have found the following two sources
> that provide excellent binary for windows.
> http://code.google.com/p/emacs-for-windows/
> http://www.ourcomments.org/Emacs/DL/EmacsW32/EmacsCVS/unptch/e
> macs-from-cvs-091015.zip
Yes, and there are other sites that also have, or have had, old Windows
binaries. And people appreciate this. But that is all beside the point.
Those you cite are from 2010/02/02 and 2009/10/15, respectively.
Neither represents the latest pretest. That's the point: the pretest.
If you, Lennart or anyone else builds a pretest binary and posts it, that will
be helpful and appreciated.
next prev parent reply other threads:[~2010-02-20 16:52 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 11:02 Next pretest, and branching plans Chong Yidong
2010-02-18 15:29 ` Drew Adams
2010-02-20 12:25 ` Leo
2010-02-20 13:05 ` Sean Sieger
2010-02-20 17:02 ` Drew Adams
2010-02-28 12:36 ` Sean Sieger
2010-02-28 15:13 ` Lennart Borgman
2010-02-20 16:52 ` Drew Adams [this message]
2010-02-20 17:35 ` Drew Adams
2010-02-20 19:45 ` Eli Zaretskii
2010-02-20 20:39 ` Drew Adams
2010-02-20 20:53 ` Lennart Borgman
2010-02-21 0:11 ` Lennart Borgman
2010-02-21 4:11 ` Eli Zaretskii
2010-02-20 17:51 ` Eli Zaretskii
2010-02-20 18:35 ` Drew Adams
2010-02-20 19:49 ` Eli Zaretskii
2010-02-20 18:36 ` Chong Yidong
2010-02-20 18:40 ` Drew Adams
2010-02-20 18:54 ` Lennart Borgman
2010-02-20 19:15 ` Drew Adams
2010-02-20 19:08 ` Lennart Borgman
2010-02-18 23:57 ` Emacs Manuals Richard Stallman
2010-02-20 2:46 ` smc
[not found] <4B8147A9.7030504@gmail.com>
[not found] ` <87ljemdzxo.fsf@stupidchicken.com>
2010-02-23 5:31 ` Next pretest, and branching plans Jason Rumney
2010-02-23 18:29 ` Eli Zaretskii
2010-02-23 21:12 ` Jason Rumney
2010-02-24 6:04 ` Richard Stallman
2010-02-24 13:34 ` Sean Sieger
2010-02-24 15:05 ` Davis Herring
2010-02-24 15:18 ` Sean Sieger
2010-02-24 14:05 ` Chong Yidong
2010-02-25 14:26 ` Richard Stallman
2010-02-27 16:52 ` Johan Bockgård
2010-03-03 3:52 ` Glenn Morris
2010-03-05 0:31 ` Johan Bockgård
2010-03-13 3:10 ` Christoph
2010-03-13 7:42 ` Eli Zaretskii
2010-03-13 14:54 ` Christoph
2010-03-13 18:30 ` Stefan Monnier
2010-03-13 19:06 ` Eli Zaretskii
2010-03-14 2:38 ` Jason Rumney
2010-03-14 2:50 ` Christoph
2010-03-14 3:07 ` Jason Rumney
2010-03-14 17:55 ` Eli Zaretskii
2010-03-17 0:29 ` Christoph
2010-03-17 4:14 ` Eli Zaretskii
2010-03-17 12:44 ` Jason Rumney
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=136A0B1647B74A53A26506F872BECC6E@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@gmail.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.
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.