Master is now at frontend level 2.069.2

[Kai Nacke via digitalmars-d-ldc]

On Tuesday, 23 February 2016 at 20:40:36 UTC, Johan Engelen wrote:
> On Tuesday, 23 February 2016 at 20:11:42 UTC, Kai Nacke wrote:
>> On Tuesday, 23 February 2016 at 16:59:25 UTC, Dan Olson wrote:
>>> Nice and thanks.  I assume best practice for changes intended 
>>> for both ltsmaster and master, do pull-request to ltsmaster 
>>> first, then later merge into master?  I am thinking of my 
>>> latest arm-linux changes.
>>
>> Hi Dan!
>>
>> This is the process we need to follow. All target architecture 
>> relevant changes (ARM, AArch64, etc.), LLVM updates and maybe 
>> bug fixes (#1224, #1292) should be developed first for 
>> ltsmaster.
>
> Isn't the opposite usually done? Develop something for master, 
> and backport to LTS ?
> (perhaps less chance of introducing something bad in LTS?)

We should also not break the master branch.

I view it from the practically side: I develop against ltsmaster 
and can then merge the changes into master. Otherwise I need to 
cherry-pick the commit which is always a bit clumsy.

Regards,
Kai