[dmd-beta] Preparation for 2.65

[Andrew Edwards]

On 1/10/14, 4:36 PM, Brad Roberts wrote:
> 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.
>
point taken
>>      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.
>
Except that _nothing_ is getting ported back to the branches. I'm still 
waiting on changes that have been made in master starting in early 
December (including regressions) to make it to the 2.065 branch. This is 
just not happening. Regarding multiple regressions, merging to branch 
and porting to master accomplishes the same thing with less confusion. 
Every change made in the branch will need to move forward to master, not 
so the other way around. The added (and more important) benefit is that 
the branch does not get overlooked.
>>      c. merge of pulls made against master should be suspended
>
> wrong.  see a.
I disagree here. Keep in mind that I'm discussing the first beta here. 
I'm also only speaking to Core Devs here: not volunteers at large. 
Attention can go back to master as soon as [e] (below) is done.
>
>>      d. attention given to outstanding regressions
>
> ideally, but volunteers spend time where they wish.
No one is asking anybody to volunteer on things they are not interested 
in. There is however an obligation to resolve issues that are impeding 
the release process and this is definitely one of them. If I'm to wait 
on all regressions to be fixed prior to starting the next release 
process, it will never happen. There are still regressions out there 
before I took on the responsibility of managing releases. Who is 
assigned to resolve them? When do we anticipate a resolution? If no one 
accepts this responsibility then I would suggest that what we've had up 
to this point is as good as we'll ever get.
>
>>      e. upon resolution of final regression, the tag is created and 
>> the beta built and released
>
> correct.
>
>
> _______________________________________________
> dmd-beta mailing list
> dmd-beta at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta