Re: Release branch plans

[Eli Zaretskii]

> From: Chong Yidong <address@hidden>
> Date: Mon, 02 Apr 2012 13:38:51 +0800
> 
> Now that the 24.0.95 pretest is out, we plan to cut the 24.1 branch
> soon.  After that is done, fixes that should go into 24.1 should be
> committed into the branch, then merged into the trunk.

Could we _please_ do it the other way around this time?  That is,
commit to the trunk and merge to the branch?  Merging from the branch
makes it hard to find out where some changes came from and why,
because history metadata says some revisions were merged, but their
code was not really brought to the target branch.  If one of the
branches has to sustain such damage, let it be other than the main
branch, if only because the life of the release branches is much
shorter; after some time no one looks at them anymore.

Please?...