On Fri, Mar 27, 2015 at 07:21:10PM +0100, Martin Nowak via Digitalmars-d wrote:
We replace the old cherry-pick approach by introducing stable branches,
more info here http://wiki.dlang.org/DIP75#Branching_strategy.
+1. It's about time! Thanks for making it finally happen!!
--T
On 3/27/15 11:28 AM, H. S. Teoh via Digitalmars-d wrote:
On Fri, Mar 27, 2015 at 07:21:10PM +0100, Martin Nowak via Digitalmars-d wrote:
We replace the old cherry-pick approach by introducing stable branches,
more info here http://wiki.dlang.org/DIP75#Branching_strategy.
+1. It's about time!
On Friday, 27 March 2015 at 18:21:32 UTC, Martin Nowak wrote:
We replace the old cherry-pick approach by introducing stable
branches,
more info here http://wiki.dlang.org/DIP75#Branching_strategy.
[snip]
Sounds good. It's not clear who will be merging stable into
master and when (it's a
Good to hear!
Unfortunately github doesn't allow to retarget pull requests,
so if a
pull targets the wrong branch, it needs to be reopened.
The targeted branch is only important for three reasons:
1. Documents the intent of the pull request (the specific point
release being targeted)
2.
On Friday, 27 March 2015 at 21:37:23 UTC, Brad Anderson wrote:
It's not clear who will be merging stable into master and when
(it's a shame Github doesn't let you target multiple branches).
Not sure we need a strict rule here and it shouldn't be necessary
to do this after each merge. Could be
On 28/03/2015 7:21 a.m., Martin Nowak wrote:
We replace the old cherry-pick approach by introducing stable branches,
more info here http://wiki.dlang.org/DIP75#Branching_strategy.
This avoids having to manually identify bugfixes to be cherry-picked
into the release branch (2.067.0 is missing at
On 03/27/2015 05:25 PM, Andrei Alexandrescu wrote:
On 3/27/15 11:28 AM, H. S. Teoh via Digitalmars-d wrote:
On Fri, Mar 27, 2015 at 07:21:10PM +0100, Martin Nowak via
Digitalmars-d wrote:
We replace the old cherry-pick approach by introducing stable branches,
more info here
