'next' will be rewound and rebuilt after feature releases.

[Junio C Hamano <gitster@pobox.com>]

Junio C Hamano <gitster@pobox.com> writes:

> Nicolas Pitre <nico@cam.org> writes:
>
>> On Wed, 6 Feb 2008, Junio C Hamano wrote:
>>
>>> ...
>>> It already is part of 'next', and we have the policy of not
>>> rewinding 'next', so the record of this mistake will
>>> unfortunately be with us forever.  Sorry, Brian, Dscho and
>>> Steffen.
>>
>> Maybe you can make an exception for this time?  A single
>
> That's very tempting.
> ...
> People who follow 'next' hopefully know what goes on the list,
> so perhaps we could revise the "never rewind" rule to read "it
> will not rewind during the regular cycle, but it will be rebuilt
> once each feature release, immediately after release."

I am almost committed to this idea, and this is an advance
notice that 'next' will be rebuilt on the tip of 'master' soon.

When that happens, I'll announce the commit object name for the
old 'next' and the corresponding new one, to make rebasing
easier for people who have been following and building on top of
it.

For tonight's tree, the tip of 'next' is at 547b1cb (Merge
branch 'master' into next) and its tree matches 26f14cc (Merge
branch 'js/reflog-delete' into next) that is part of 'pu'.