[dmd-beta] Preparation for 2.65
Brad Roberts
braddr at puremagic.com
Fri Jan 10 13:36:12 PST 2014
On 1/10/14 12:50 PM, Andrew Edwards wrote:
>
> Once the branch is prepared:
> a. implementation of new features should cease
wrong, that's why there's a separation between master and a release branch.
> b. pull request for fixes should be made against and merged with the branch
wrong, fixes should _always_ be made on master first and then back ported to branches that might
require them. Consider the case of a regression that exists in multiple release branches.
> c. merge of pulls made against master should be suspended
wrong. see a.
> d. attention given to outstanding regressions
ideally, but volunteers spend time where they wish.
> e. upon resolution of final regression, the tag is created and the beta built and released
correct.
More information about the dmd-beta
mailing list