On Sat, 8 Jun 2019 at 01:04, Jorge Gustavo Rocha wrote:
> If we need to define a goal, it would be: cleanup 2/3 of the queue (and
> keep the queue below 1000 issues).
Funnily enough, I was thinking of a similar thing shortly after the
github transition and also came to the same figure as an achi
Hi,
Good idea Jorge. But I also find next week too short. And think it would be
better after release; there are likely more users that could update to 3.8 than
3.7 Dev version, most appropriate versions to test issues.
So we make the call, we spread in language communities and all channels, we
h
Hi Jorge,
I understand your aim. I think it is important to mage distributed bug
squashing parties a regular feature of our community, so better start
now, even if ideally I would wait one month after announcement. Maybe we
can have a calendar of future BSPs just after freeze for each version?
Or j
Hi Paolo,
Thanks for the feedback. You are right. The time is short, for sure. I
was trying to do it before our next release on June, 21th.
What do you think? Should we do it before the 3.8 release? Maybe on
June, 18-19? Or should we postpone it to prepare it more carefully and
get more visibilit
Olá Jorge,
I fully agree with your proposal. Limited attempts in the past have
given good results. I think more time should be allowed to let people
organize.
Cheers.
On 07/06/19 17:03, Jorge Gustavo Rocha wrote:
> Hi devs,
>
> We changed our bug tracking tool. One of the goals is to have more
>
Hi devs,
We changed our bug tracking tool. One of the goals is to have more
people doing bug triage, confirming bug reports, providing examples,
screenshots and so on. We need more [power] users involved and more
developers on the “bug triage” team.
Let’s take advantage of all these discussions a
