<html><head></head><body>Hi,<br>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.<br>So we make the call, we spread in language communities and all channels, we help and ensure that all main OSs have updated to 3.8 quickly and a week or two after release, let's massively test. And 3.10 as LTR can be an interesting and hearable argument. So I'm not fond of doing for each release and let's see how this one plays yet.<br><br>Regards,<br>Harrissou<br><br><div class="gmail_quote">Le 8 juin 2019 13:54:47 GMT+02:00, Paolo Cavallini <cavallini@faunalia.it> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi Jorge,<br>I understand your aim. I think it is important to mage distributed bug<br>squashing parties a regular feature of our community, so better start<br>now, even if ideally I would wait one month after announcement. Maybe we<br>can have a calendar of future BSPs just after freeze for each version?<br>Or just for LTR, not to wear out volunteers too early?<br>Cheers.<br><br>On 08/06/19 12:34, Jorge Gustavo Rocha wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Hi Paolo,<br><br>Thanks for the feedback. You are right. The time is short, for sure. I<br>was trying to do it before our next release on June, 21th.<br><br>What do you think? Should we do it before the 3.8 release? Maybe on<br>June, 18-19? Or should we postpone it to prepare it more carefully and<br>get more visibility?<br><br>Regards,<br><br>Jorge<br><br>Às 10:44 de 08/06/19, Paolo Cavallini escreveu:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> Olá Jorge,<br> I fully agree with your proposal. Limited attempts in the past have<br> given good results. I think more time should be allowed to let people<br> organize.<br> Cheers.<br><br> On 07/06/19 17:03, Jorge Gustavo Rocha wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"> Hi devs,<br><br> We changed our bug tracking tool. One of the goals is to have more<br> people doing bug triage, confirming bug reports, providing examples,<br> screenshots and so on. We need more [power] users involved and more<br> developers on the “bug triage” team.<br><br> Let’s take advantage of all these discussions around the tool and the<br> changes introduced, to focus on what is really important: to have more<br> people involved in QGIS testing to provide more stable releases. To tool<br> is not the goal.<br><br> We need to clean up our bug/feature request queue. We already had good<br> proposals here on the list, regarding cleaning old issues and pointing<br> to new policies regarding issue lifetime. We just need more action!<br><br> Proposal<br><br> My proposal is to publish a post on our blog calling for a huge QGIS Bug<br> Squash party, for two days, making all users aware of this new tool and<br> calling them for this activity. We can ask them (for example) to<br> selected 5 issues they can improve, by providing more feedback<br> (confirming a bug report in current 3.x version, for example) or by<br> subscribing a feature request they found important.<br><br> To provide live support for all users involved in the party, I would<br> like to create a Doodle to make sure we have at least one developer<br> available on IRC/Gitter (for the all 48 hours) where people can discuss<br> what to do with ticket X. Each developer would subscribe a 4 hour period<br> (that’s the usual watchkeeping period for sailors).<br><br> I also would like to propose to the PSC/this developer list that current<br> committers can have the “triage” role on qgis/QGIS - upon request - to<br> have more people doing bug triage. Régis and Saber already mentioned<br> this limitation regarding issue management and both are well known<br> contributors (and Saber can follow 3D tickets ;-)) For those seeking to<br> join the “bug triage” team, they just need to have a PR committed (and<br> they will be rewarded).<br><br> QGIS Bug Squash party goal<br><br> If we need to define a goal, it would be: cleanup 2/3 of the queue (and<br> keep the queue below 1000 issues).<br><br> Comments<br><br> Please provide comments about this proposal. For the exact dates for the<br> party, I suggest 14 and 15 (next week) to have a regular working day<br> (for those able to work on QGIS on their daily jobs) and Saturday, for<br> the ones only working on their spare time.<br><br> Regards,<br><br> J. Gustavo<br><br></blockquote></blockquote>J. Gustavo<br><br></blockquote></pre></blockquote></div><br>-- <br>Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.</body></html>