<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p>Last year I uploaded an addon and realised just afterwards that
there was an error... I had to wait for the first one to be passed
and then upload another. I was really glad that the submissions
were both processed very quickly. <span class="moz-smiley-s1"><span>:-)</span></span>
Maybe in a matter of days!<br>
</p>
<p>Could there be a delete button on the manage your submissions
page? <br>
</p>
<p>Also when it becomes essential to update to MailExtensions there
could be a bit of a queue develop... is there any preparation for
this?</p>
<p>While thinking about MailExtensions, I've been wondering for a
while, could I upload my MailExtensions addon which is working,
with a minimum version set at 61? Would earlier Thunderbird
versions ignore the newer version? <br>
</p>
<p>Blessings<br>
Graeme<br>
</p>
<div class="moz-cite-prefix">On 20/03/2019 19:05, Ryan Sipes wrote:<br>
</div>
<blockquote type="cite"
cite="mid:dd3cc253-3203-afbc-bda0-e2db1a350fd2@thunderbird.net">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<p>I have a few thoughts on this.</p>
<p>1) We need to further define what gets escalated to admin
review status. As that is the biggest bottleneck and I'm not
sure those that get escalated always deserve it.<br>
</p>
<p>2) We need dedicated admin reviewers to ensure that reviews are
getting done on those.</p>
<p>3) We need transparency on how many add-ons are in review and
probably need that to hit the community so that folks can track
when their help is needed. But at the very least it needs to hit
the add-on reviewers mailing list.</p>
<p>Anyone who wants to become an add-on reviewer can fill out this
form: <a class="moz-txt-link-freetext"
href="https://goo.gl/forms/o0FFYmx5bfpjVZgv2"
moz-do-not-send="true">https://goo.gl/forms/o0FFYmx5bfpjVZgv2</a></p>
<p>We can always use more hands working on this problem.<br>
</p>
<pre class="moz-signature" cols="72">Ryan Sipes
Community Manager
Thunderbird</pre>
<div class="moz-cite-prefix">On 3/20/19 10:47 AM, Mark Rousell
wrote:<br>
</div>
<blockquote type="cite" cite="mid:5C926EBE.7090308@signal100.com">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Typo fix...<br>
<br>
On 20/03/2019 15:02, Mark Rousell wrote:<br>
<blockquote cite="mid:5C9255F6.5030406@signal100.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
And people do not necessarily always agree on the directions
making collaboration non-sensical, and so forking can be a way
for competing views to find the approach that best suits the
preferences of users.<br>
</blockquote>
<br>
s/people do not necessarily always agree on the directions
making/people do not necessarily always agree on project
directions thus making/<br>
<br>
<pre class="moz-signature" cols="72">--
Mark Rousell
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
tb-planning mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org" moz-do-not-send="true">tb-planning@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning" moz-do-not-send="true">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
tb-planning mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
</body>
</html>