From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dag@gnui.org, liwei.ma@gmail.com, emacs-devel@gnu.org,
kevin.legouguec@gmail.com
Subject: Re: Do pretests reach end users?
Date: Fri, 3 Jul 2020 23:23:16 +0300 [thread overview]
Message-ID: <6d111f05-9512-c618-7e32-cd4bd88e28c6@yandex.ru> (raw)
In-Reply-To: <834kqox1qv.fsf@gnu.org>
On 03.07.2020 14:43, Eli Zaretskii wrote:
>> From: Dmitry Gutov<dgutov@yandex.ru>
>> Date: Fri, 3 Jul 2020 12:59:31 +0300
>> Cc:liwei.ma@gmail.com,kevin.legouguec@gmail.com,emacs-devel@gnu.org
>>
>>>> And even pretest releases for Windows do not seem to be mentioned in any way on<https://gnu.org/s/emacs>. How users are supposed to get them?
>>> They aren't. We cannot control the policies of the various distros,
>>> and cannot rely on them for being part of the pretest. Sometimes they
>>> are, nonetheless, presumably because the people who are responsible
>>> for the distros read the announcements about the pretests, and that is
>>> good. But it isn't the main means for pretesting.
>> What about the official website, though?
> What about it?
I can/should contain information on how to try the "next" version.
There are no links to development snapshots and related instructions. No
quickly available information on how to participate in the project (one
needs to click on "Documentation & Support" scroll down and then find
the word "CONTRIBUTE" at the very end of the page).
Improving on any of these can increase the number of users trying out
our development snapshots and reporting bugs. Which should lead to
faster stabilization.
next prev parent reply other threads:[~2020-07-03 20:23 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 2:52 When will emacs 27.1 be officially released? Liwei Ma
2020-06-30 3:55 ` Eli Zaretskii
2020-06-30 8:12 ` tomas
2020-06-30 9:51 ` Kévin Le Gouguec
2020-06-30 16:58 ` Eli Zaretskii
2020-06-30 18:52 ` Paul Eggert
2020-06-30 19:06 ` Eli Zaretskii
2020-06-30 22:17 ` Paul Eggert
2020-06-30 22:31 ` Dmitry Gutov
2020-07-01 0:03 ` Paul Eggert
2020-07-01 14:29 ` Eli Zaretskii
2020-07-01 17:47 ` Dmitry Gutov
2020-07-01 17:52 ` Paul Eggert
2020-07-01 17:55 ` Dmitry Gutov
2020-07-01 18:13 ` Eli Zaretskii
2020-07-01 18:16 ` Dmitry Gutov
2020-07-01 18:12 ` Eli Zaretskii
2020-07-01 14:33 ` Eli Zaretskii
2020-07-02 3:49 ` Richard Stallman
2020-07-02 13:04 ` Eli Zaretskii
2020-07-03 2:21 ` Richard Stallman
2020-07-02 20:29 ` Tassilo Horn
2020-07-02 20:36 ` Paul Eggert
2020-07-02 20:55 ` Tassilo Horn
2020-07-04 2:53 ` Richard Stallman
2020-07-04 6:41 ` Eli Zaretskii
2020-07-05 2:35 ` Richard Stallman
2020-07-05 14:33 ` Eli Zaretskii
2020-07-03 6:05 ` Eli Zaretskii
2020-07-03 7:24 ` Tassilo Horn
2020-07-03 11:59 ` Eli Zaretskii
2020-07-04 2:52 ` Richard Stallman
2020-06-30 22:09 ` Kévin Le Gouguec
2020-07-01 14:49 ` Eli Zaretskii
2020-07-02 9:00 ` Kévin Le Gouguec
2020-07-02 13:12 ` Eli Zaretskii
2020-07-02 13:44 ` Kévin Le Gouguec
2020-07-03 0:48 ` Do pretests reach end users? (was: When will emacs 27.1 be officially released?) Dmitry Alexandrov
2020-07-03 6:21 ` Eli Zaretskii
2020-07-03 9:59 ` Do pretests reach end users? Dmitry Gutov
2020-07-03 11:43 ` Eli Zaretskii
2020-07-03 20:23 ` Dmitry Gutov [this message]
2020-07-04 6:15 ` Eli Zaretskii
2020-07-04 1:31 ` Dmitry Alexandrov
2020-07-04 6:32 ` Eli Zaretskii
2020-07-05 4:18 ` Dmitry Alexandrov
2020-07-04 11:11 ` Phillip Lord
2020-07-05 4:23 ` Dmitry Alexandrov
2020-07-05 21:15 ` Phillip Lord
2020-07-05 16:55 ` Sean Whitton
2020-06-30 13:01 ` When will emacs 27.1 be officially released? Basil L. Contovounesios
2020-06-30 14:06 ` Stefan Monnier
2020-06-30 14:28 ` Eli Zaretskii
2020-06-30 14:34 ` Rostislav Svoboda
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=6d111f05-9512-c618-7e32-cd4bd88e28c6@yandex.ru \
--to=dgutov@yandex.ru \
--cc=dag@gnui.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=liwei.ma@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.