Re: Next release from master

[Michael Albinus]

Eli Zaretskii <address@hidden> writes:

> This problem should only exist with externally maintained packages
> that are then merged into Emacs's repository.  If such a package has
> faster release schedule, it might have such a problem because some
> change not appropriate for the Emacs release branch doesn't want to
> wait for the next major Emacs release.

Counter example: kqueue integration. It was a candidate for 25.1, but
didn't reach it because it was one or two weeks too late.

That was two months ago ... and now, according to that plan, it would be
postponed until Emacs 26 appears. There's even no pretest for Emacs 25.1
until now.

Best regards, Michael.