Re: decision on moving core packages to ELPA; also move to obsolete?

[Eli Zaretskii]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Stephen Leake <stephen_leake@stephe-leake.org>,  daniele@grinta.net,
>   emacs-devel@gnu.org
> Date: Tue, 15 Dec 2020 14:54:52 -0500
> 
> > So please describe how you envision the process of building a release
> > tarball under this assumption.  E.g., how do I know which version of
> > package A I want to bundle is stable enough to go to a bugfix elease
> > of Emacs?
> 
> I'd expect it to work the same as for Org, MH-E, Gnus, you name it.

What do you mean by "the same as"?  Currently, it is not our decision
which Org/MH-E/etc. version will be in what Emacs branch.  The
respective developers make that decision and simply push the version
they decided into our repository.

Once we separate the repositories, the decision will have to be made
by whoever prepares the tarball, and I don't see how he or she could
be equipped to make that decision, nor how the packages are organized
for this modus operandi.

> But your question is getting to the more meaty stuff indeed: the problem
> of bundling is one of making decisions/tradeoffs.  The actual code
> needed to do the bundling is quite simple and most of it is
> already written.

I'm not sure most of it is done.  Over the years, we had several long
discussions here about this stuff, and AFAIR none of them ended with
solutions.  All those issues raised in those discussions are still
with us, waiting to bite us.

We need to go over those issues and solve them before we can seriously
talk about unbundling ada-mode or any other package.