Re: [Bf-committers] 2.8 bugs on the tracker.

On 7/2/2018 8:03 PM, Ray Molenkamp wrote: > T55706 is a less clear duplicate of T52523 (and T55706 has a not so useful > title, so even if they did search it wouldn't have been found) sorry got my tickets mixed up here, it's a duplicate of T55695. --Ray

[Bf-committers] 2.8 bugs on the tracker.

All, Since the tracker has now been opened for 2.8 crashes tickets have been coming in steadily, I'm unsure how to triage these though, previously it was easy, just the studio tickets were allowed and they placed them on the 2.8 work board them selves. Is tagging the end user tickets with just

Re: [Bf-committers] 2.8 bugs

Limiting peoples access is not the way we want to go. I think the current system of copy pasting a canned answer is fine. We dont want to discourage people from trying it out and reporting bugs. By the time we need this people might not do this. On Sat, Mar 3, 2018 at 8:50 PM, Ricardo Nunes

Re: [Bf-committers] 2.8 bugs

Best way would probably be to just limit the access. No matter how clear it is people online are notoriously bad at listening.. On 4 Mar 2018 02:07, "Ray Molenkamp" wrote: > Hey, > > Is there anything we can do to make the text on > https://builder.blender.org/download/

[Bf-committers] 2.8 bugs

Hey, Is there anything we can do to make the text on https://builder.blender.org/download/ regarding 2.8 bugs stand out a little more. This text is currently under some brightly color buttons in all black. -- Note on Blender 2.8 builds Currently we are aware of many issues in 2.8 and actively