[Bf-committers] Suggestions for improving the triaging process

2020-11-23 Thread Philipp Oeser via Bf-committers
Hi all, there was some recent talk amongst triagers about some issues / open questions in our triaging process. This mail tries to sum them up and bring forth possible ways to improve here. Feedback is welcome, everyone interested is also invited to join the new https://blender.chat/channel/blen

[Bf-committers] #blender-triagers channel on blender.chat

2020-11-24 Thread Philipp Oeser via Bf-committers
Hi all, I would like to welcome everyone interested in triaging (bug-)reports on https://developer.blender.org/ to join our new channel on blender.chat which can be found at https://blender.chat/channel/blender-triagers This channel is home to discussions regarding the general process of triag

[Bf-committers] changed naming of two report status types on developer.blender.org

2021-03-10 Thread Philipp Oeser via Bf-committers
Hello everyone! Today we have changed the naming of two report status types on developer.blender.org: - [1] "Needs Developer to Reproduce" > "Needs Information from Developers" - [2] "Invalid" > "Archived" Reasoning: For [1], this already came up here [a], but I will try to explain again: the "N

[Bf-committers] Corrective 3.0.1 release

2022-01-11 Thread Philipp Oeser via Bf-committers
Hi all! I have pushed the fixes for a corrective 3.0.1 release [*] to the blender-v3.0-release branch now. Has a nice list of 77 fixes already, thx! Propose to release this either next Wednesday [19.01.2022] or - if we want more testing in that branch or give developers a chance to tackle any of

Re: [Bf-committers] Corrective 3.0.1 release

2022-01-18 Thread Philipp Oeser via Bf-committers
Oeser via Bf-committers wrote: > Hi all! > > I have pushed the fixes for a corrective 3.0.1 release [*] to the > blender-v3.0-release branch now. > Has a nice list of 77 fixes already, thx! > > Propose to release this either next Wednesday [19.01.2022] or - if we > want more t