Re: New Package for NonGNU-ELPA: clojure-ts-mode

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sun, 27 Aug 2023 16:12:00 +0300
> Cc: Eli Zaretskii <eliz@gnu.org>, philipk@posteo.net, danny@dfreeman.email,
>  stefankangas@gmail.com, emacs-devel@gnu.org, manuel.uberti@inventati.org
> From: Dmitry Gutov <dmitry@gutov.dev>
> 
> On 27/08/2023 15:57, Po Lu wrote:
> > Dmitry Gutov<dmitry@gutov.dev>  writes:
> > 
> >> We could easily have more frequent releases, it's all in the hands of
> >> the maintainers, actually. Stability/velocity tradeoffs.
> > Producing another atrocity following the footsteps of Mozilla?  No
> > thanks!
> 
> Releasing a new Emacs, say, even 6 month won't suddenly turn it into a 
> crashing mess.

We already do it, or thereabouts.  Check out the last part of
etc/HISTORY.

> But we would get more and faster feedback for new features and
> changes.

Maybe, maybe not.  See below.

> That's the main issue why we have to drag on the release schedule: we 
> don't get reports of regressions soon enough after introducing them. So 
> we have to wait months for the users to try and report back.
> 
> How to change that? Either make releases more often, or make snapshot 
> releases more prominent and easier to try, or improve the bug reporting 
> experience so that more people do that. Or all of that together, of course.

Are you sure this will help?  Here's a typical case:

  https://lists.gnu.org/archive/html/help-gnu-emacs/2023-08/msg00454.html

This guy just recently upgraded to Emacs 29, and is reporting a
significant issue only now, a month after Emacs 29.1 was released.

I've seen similar things many times: people upgrade to a new Emacs
version months, and sometimes years, after that version was released.
Try to collect feedback for a release quickly given this upgrade
schedule.

> I wonder what wonderful curious bug reports we would also get if we had 
> the number of users that Firefox has.

If we never do anything, we will keep wondering, and it will remain
forever in the "he said, she said" department.