[dmd-beta] 2.065 Final Release Prep

[David Nadlinger]

On 27 Feb 2014, at 19:30, Andrew Edwards wrote:
> David, I honestly think this is a waste of time. Since nothing is
> directly implemented into 2.065 (everything contained in it were
> either cherry-picked directly or via pull request from master) […]

If you are sure that there are no commits on the release branch that are
not in master (there have been issues with this in the past), just
create a merge commit, resolving all the differences by defaulting to
the master version (cf. merge strategies) or just setting the content of
the merge commit to master.

> This is a lot of time wasted [f]or zero gain

In (your) "[dmd-beta] Preparation for 2.65" thread, I explained in
considerable detail why we need to do precisely the same thing when
merging the release into LDC later, only that we don't have the
knowledge of what exactly happened in the release phase.

If you have suggestions on how to better handle the situation, be sure
to let me know though.

David