Re: Feature freezes and Emacs 25

[Juri Linkov]

>> I think we should first decide whether new features that are "almost ready"
>> should or should not be in 25.1. Two examples that immediately come to mind
>> are dynamic loading and xwidgets; I don't know if there are others. After we
>> make the decision, we could see if one week's time is enough.
>
> I'd like to see both of those in 25.1.
>
> Let's freeze this Friday, and take a step back. We have several courses open:
>
>  1. Decide that what we have now should become 24.6.
>
>  2. Decide it will become 25.1.
>
>  3. Decide that we want to bring in more features that aren't yet complete,
>     and so push the freeze to a future date.

John, could you please extend the deadline of the feature freeze a little
since I have no chance to commit all changes until Friday.

Basically what I'm doing is the same kind of work as Alan's efforts in 
bug#17453.
While Alan is designing a framework to support multiple windows
by adding a new arg with a group of windows, I'm designing a framework
to support multiple regions by adding a new arg with a group of regions.

In bug#19829 I've collected the evidence of commands that need this
feature as a basis for the new design, but the deadlock was caused by the
same question that backpedaled the Alan's design: whether to add a new arg
to the existing functions or to try stuffing it into the existing ones?