[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ANNOUNCE] Emacs 25.3 released

From: Thien-Thi Nguyen
Subject: Re: [ANNOUNCE] Emacs 25.3 released
Date: Tue, 12 Sep 2017 20:26:10 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)

() Eli Zaretskii <address@hidden>
() Tue, 12 Sep 2017 19:52:26 +0300

   Getting the Git repository in order is much less urgent than
   putting the tarball out the door, so I asked Nicolas to do
   that in this order.  I don't see why this small lag is so
   important.  Given the nature of the problem, the priorities
   were clear, I don't think they can be controversial.

I think the lag is important because it represents "attack
surface" (for FUD) to defend.  Look at all the noise already
precipitated.  A few seconds doing "git {commit, tag, push}"
benefits everyone interested in skipping this noise, greatly.

If those operations are not sufficient to get the repo in order,
then i suggest they be done prior to tarball publication,
anyway, but on a provisional branch.  Afterwards, the proper
"getting the repo in order" operations can work w/ that branch
to merge it back to ‘master’ or whatever.

In sum: IMHO it's fine to deviate from full release protocol if
the deviation maintains transparency.  When transparency is
lost, we need (annoying :-D) ml threads to find it again.

Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)
   (pcase (context query)
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]