all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Phillip Lord <phillip.lord@russet.org.uk>
To: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
Cc: Eli Zaretskii <eliz@gnu.org>, Corwin Brust <corwin@bru.st>,
	emacs-devel@gnu.org
Subject: Re: Emacs 29.0.50 Snapshot binaries for WIndows
Date: Fri, 18 Feb 2022 18:18:05 +0000	[thread overview]
Message-ID: <87wnhsxcma.fsf@russet.org.uk> (raw)
In-Reply-To: <86bkz5u0la.fsf@duenenhof-wilhelm.de> (H. Dieter Wilhelm's message of "Thu, 17 Feb 2022 13:41:37 +0100")

"H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>
> @Corwin: Do you also have wright access to ftp.gnu.org for the upcoming
> release?
>
> Is it really worth the burden to build snapshots of the release
> branch-28, when there are pretests out?


I wouldn't. It risks confusing things (especially if the snapshots get
behind the pretest!).

I used to build snapshots master branch and sometimes the release
branch before the pre-tests. Occasionally, I used to build other
branchs as well (the pdumper branch was the main one). You might be able
to get stats from the website logs to see whether this was worth while
or not! I would guess "when there is a new feature" is probably as good
as a regular release.

Phil



  reply	other threads:[~2022-02-18 18:18 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  3:37 Emacs 29.0.50 Snapshot binaries for WIndows Corwin Brust
2022-02-17  6:38 ` Eli Zaretskii
2022-02-17 12:41   ` H. Dieter Wilhelm
2022-02-18 18:18     ` Phillip Lord [this message]
2022-02-19  4:57 ` Richard Stallman
2022-02-19  5:09   ` Po Lu
2022-02-19  8:40   ` Eli Zaretskii
2022-02-20  4:31     ` Richard Stallman
2022-02-20  4:34       ` Po Lu
2022-02-21  4:35         ` Richard Stallman
2022-02-21  4:57           ` Po Lu
2022-02-23  6:46             ` Richard Stallman
2022-02-21  5:18           ` Eli Zaretskii
2022-02-21 12:06           ` Tim Cross
2022-02-21 18:41             ` chad
2022-02-21 19:38               ` Eli Zaretskii
2022-02-22  1:08                 ` Po Lu
2022-02-20  6:46       ` Eli Zaretskii
2022-02-21  4:35         ` Richard Stallman
2022-02-21 11:57         ` Dmitry Gutov
2022-02-24 22:41       ` phillip.lord
2022-02-19 11:14   ` Corwin Brust
2022-02-21  4:34     ` Richard Stallman
2022-02-23 14:33       ` Corwin Brust
2022-02-23 16:41         ` Stefan Monnier
2022-02-23 23:07           ` Corwin Brust
2022-02-24  6:55             ` Eli Zaretskii
2022-02-25  4:55               ` Corwin Brust
2022-02-25 11:28                 ` Phillip Lord
2022-02-25  5:00         ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2023-02-01  7:36 c.buhtz
2023-02-01 20:24 ` Corwin Brust
2023-02-19  9:56   ` c.buhtz
2023-02-19 18:05     ` Corwin Brust
2023-02-24  5:33       ` Troy Brown
2023-02-24  6:43         ` c.buhtz
2023-02-24  8:22           ` Eli Zaretskii
2023-02-24  8:47             ` c.buhtz
2023-02-24 11:40               ` Eli Zaretskii
2023-02-24 21:01                 ` c.buhtz
2023-02-24 21:17                   ` Eli Zaretskii
2023-02-24 21:42                     ` c.buhtz
2023-02-25  9:53                       ` Eli Zaretskii
2023-02-26 15:17                     ` c.buhtz
2023-02-26 15:48                       ` Eli Zaretskii
2023-03-10 18:49         ` Corwin Brust

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=87wnhsxcma.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=corwin@bru.st \
    --cc=dieter@duenenhof-wilhelm.de \
    --cc=eliz@gnu.org \
    --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.