If there were changes in the 2.065 branch that weren't in master (there doesn't appear to be but it needs to be double checked) they need to be merged back into master before the branch is deleted so they aren't lost.

I just had to make https://github.com/D-Programming-Language/dmd/pull/3080 after noticing (just by chance) that the latest version was missing from master.

We almost got to the release stage with that missing from master because the release branch was never merged back into master.


On Sun, Jan 12, 2014 at 11:38 PM, Walter Bright <walter@digitalmars.com> wrote:

On 1/12/2014 10:12 PM, Brad Anderson wrote:
The branches need to be cleaned up to make this release anyway. I don't see how calling it 2.066 would make doing this any easier.

If the 2.065 branch is skipped, why would it need cleaning up?


_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta