Re: When will emacs 27.1 be officially released?

[Kévin Le Gouguec]

Eli Zaretskii <eliz@gnu.org> writes:

> Development snapshots are just that: snapshots of the current
> repository's master branch.  As such, they are irrelevant to the issue
> at hand, because we are talking about releases, not snapshots.

My reasoning for suggesting snapshots went something like:

1. A lot of time passes between changes being committed, and users
   reporting regressions caused by these changes.

2. How could we tighten this feedback loop, so that we can spend less
   time gritting our teeth and waiting for bug reports during pretests?

3. If we offered development snapshots, maybe some users would feel
   adventurous enough to try them, and maybe some of them would even
   report bugs.

4. When we cut a release branch, we could feel more confident about the
   lack of regressions, because the most severe ones will have been
   caught thanks to snapshots.

Granted, maybe the intersection between "wants the bleeding edge" and
"won't run git pull" is an empty set, and snapshots would not bring
significantly more exposure to the master branch 🤷

>> > I think it was 26.3, and the problem is not the decision, the problem
>> > was how much time it took.  Too much, IMO.
>> 
>> 25.3 was the "⚠🚨 Red alert! Enriched Text is insecure! 🚨⚠" release
>
> Time flies; sorry for misremembering.

It sure does; I had misremembered too and had to to a double-take :)