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

[Eli Zaretskii]

> From: Philip Kaludercic <philipk@posteo.net>
> Cc: dmitry@gutov.dev,  luangruo@yahoo.com,  danny@dfreeman.email,
>   stefankangas@gmail.com,  emacs-devel@gnu.org,
>   manuel.uberti@inventati.org
> Date: Sun, 27 Aug 2023 14:13:56 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Philip Kaludercic <philipk@posteo.net>
> >> Cc: Po Lu <luangruo@yahoo.com>,  Eli Zaretskii <eliz@gnu.org>,
> >>   danny@dfreeman.email,  stefankangas@gmail.com,  emacs-devel@gnu.org,
> >>   manuel.uberti@inventati.org
> >> Date: Sun, 27 Aug 2023 13:25:49 +0000
> >> 
> >> BTW. what is the current system by which releases are cut?  I don't know
> >> if the maintainers have a schedule or some general plan for internal
> >> usage.
> >
> > I don't know how to answer this.
> 
> How did you decide when to draw the line between Emacs 29 and Emacs 30?

That's when the release branch is cut.  But doing so doesn't determine
the future release date, except very roughly.

When to cut the release branch is up to the maintainers, and IME the
reasons are not fixed.  The mount of new features and the time since
the last major release are important factors, though.

> >              And why should we take them into account, and not the
> > other way around?  I have never seen a Debian (or any other distro)
> > approach us asking when the next release is expected.
> 
> That is true, but I don't see any reason why there shouldn't be any
> cooperation.

Neither do I, but cooperation is a two-way street.

There's also a problem that we rarely can promise a certain release
date, because there are factors out of our control, such as the bugs
and regressions reported during pretest, the resources that can
dwindle due to "Real Life", etc.