[Bf-committers] Blender 2.79a Release Candidate AHOY

2018-01-23 Thread Sergey Sharybin
Hi everyone, A huge work was done to port crucial fixes (and even more!), and we are ready for 2.79a Release Candidate now. Yes, that's right. There are so much things that changed, that we do an extra steps for corrective release, something we didn't do before. Full list of changes can be found

Re: [Bf-committers] Blender 2.79a Release Candidate AHOY

2018-02-01 Thread Gaia Clary
i found a nasty mistake in one of my recent fixes where i have unintentionally commented out 2 lines which now disable Collada animation export. Please can you consider to add this fix to 2.79a? rB78a77fe622b8 -- fix: unintentionally commented out collada animation export thanks, Gaia On 2

Re: [Bf-committers] Blender 2.79a Release Candidate AHOY

2018-02-01 Thread Joshua Leung
While we're at it, all of the NLA/Driver/Breakdowner fixes under the "To be considered?" section can be included Joshua On Fri, Feb 2, 2018 at 1:03 PM, Gaia Clary wrote: > i found a nasty mistake in one of my recent fixes where i have > unintentionally commented out 2 lines which now disable Co

Re: [Bf-committers] Blender 2.79a Release Candidate AHOY

2018-02-02 Thread Bastien Montagne
Eh… for some reason, we don't have same code in 2.79a and master for DocumentWriter.cpp, and that issue is not present in 2.79a afaict. Would be nice if you could double-check that though. But rB78a77fe622b8 does not apply cleanly and is not needed on 2.79a imho. Bastien Le 02/02/2018 à

Re: [Bf-committers] Blender 2.79a Release Candidate AHOY

2018-02-02 Thread Bastien Montagne
Am sorry, but that kind of changes cannot be considered as totally safe/straightforward, which is why they were put in 'to be considered' category instead of being backported right away. Devs had over a month to check on that public list and say which of their commits they wanted to be included

Re: [Bf-committers] Blender 2.79a Release Candidate AHOY (rB78a77fe622b8)

2018-02-02 Thread Gaia Clary
Sorry for the noise. I thought i messed up something but actually all is well. Although the story behind it is a bit odd: The breakage actually happened with commit 6febe6e72 which was labelled "Silence warning from Collada". The commit slipped through my attention (my fault) so i was not awar