<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-CA link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This whole discussion has confused me.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The idea is if you try to push out crappy updates where barely anything has changed, the review will stop and you can re-submit when more things have changed.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I'm not sure why anyone is arguing against this? If you have meaningful updates every couple of days I don't think anyone would complain.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> theme-reviewers [mailto:theme-reviewers-bounces@lists.wordpress.org] <b>On Behalf Of </b>Chip Bennett<br><b>Sent:</b> Saturday, July 26, 2014 2:00 PM<br><b>To:</b> Discussion list for WordPress theme reviewers.<br><b>Subject:</b> Re: [theme-reviewers] Frequent Updates<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>If you're pushing out meaningful updates, then nothing said here applies to you.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Sat, Jul 26, 2014 at 3:58 PM, Trent Lapinski <<a href="mailto:trent@cyberchimps.com" target="_blank">trent@cyberchimps.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Most of our themes are on the same framework as well, so we typically push core changes to all of our themes. Of which we have 14+ now that we regularly maintain with millions of downloads. We've regularly been pushing updates 1-4 times a month for 3 years now through a release schedule.<br><br>This has been debated before, and no policy was ever put in place.<br><br>Why is this suddenly an issue again?<br><br>If it's really that big a deal we can move to a biweekly schedule, but it just means more issues per ticket. This doesn't actually reduce how much time it takes to review. This solves nothing.<br><br>For an open source community, this sure doesn't feel very "open" anymore if we can't even maintain our themes in a timely manor.<o:p></o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>--Trent Lapinski<br>CyberChimps.com<br>Sent from my iPhone<o:p></o:p></p></div><div><div><p class=MsoNormal>> On Jul 26, 2014, at 12:59 PM, Bryan Hadaway <<a href="mailto:bhadaway@gmail.com">bhadaway@gmail.com</a>> wrote:<br>><br>> Keep in mind also that we at CyberChimps have a HUGE community with millions of downloads, therefore we receive a ton of bug reports.<br>><br>> There are so many variables these days between OS, browser, browser version, computers, mobile devices, WordPress version, plugins etc. etc. etc. that I would assume there are many issues in most themes in the repo now, they just don't happen to have as many people using those themes in which to discover and report these edge-case issues as quickly.<br>><br>> Development is closely aligned with our support department and we streamline customer support issues that turn out not to be just isolated issues into theme fixes very quickly.<br>><br>> That's just our natural workflow, and it's constant and neverending.<o:p></o:p></p></div></div><div><div><p class=MsoNormal>> _______________________________________________<br>> theme-reviewers mailing list<br>> <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>_______________________________________________<br>theme-reviewers mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br><a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>