Re: Post-22.1 development?

[David Kastrup]

Richard Stallman <address@hidden> writes:

>     FWIW, I don't think we should merge changes that are safe until
>     some time has passed and we have some kind of idea about how
>     buggy v22.1 is.  If the number of problems we hear on
>     bug-gnu-emacs is large, then we should stabilize 22.x before we
>     merge changes that can potentially destabilize it.
>
> We need to see, first of all, how many problems are reported in
> 22.1.

Why do we need to see that?  Problems in 22.1 will be of two kinds:

a) Problems that have a better fix or solution in Emacs 23
b) Problems that have the same fix or solution in Emacs 23

In case a, we need to synchronize 2 solutions into three branches
(EMACS_22_BASE, trunk and unicode-2), in case b we need to synchronize
one solution into three branches.

That is one branch too many.  We are working towards two release
series at most (22.x and 23.1).  Branches in CVS are enough of a pain
that we don't want to keep three branches for two goals.

> We don't know how many Emacs 22 releases will be needed at all.

It does not matter.  We have the EMACS_22_BASE branch to cater for
them.  It is not like we are betting everything on the trunk.

-- 
David Kastrup