RE: GIT mirror of Lisp dev sources [was: Char-folding: how can we implement matching...]

[Drew Adams]

> > > (Why doesn't master hold the latest developments, just as
> > > (IIUC) it has always done in the past?)
> >
> > During release stabilization, at least in recent releases that
> > I can remember, the maintainers have asked that changes go to
> > the release branch first and then get ported to 'master' later.  
> 
> Except for new features, that is. The emacs-25 branch is for
> refining what will get release. The master branch is still
> the place where we add brand new stuff.

This is a new feature, is it not?  Are we supposed to look to
`master' only for an initial implementation of a new feature,
and then look to an `emacs-N' branch for its post-branching
improvement?