<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=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@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:0cm;
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.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
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=DE link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This would be my preferred solution. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
theme-reviewers-bounces@lists.wordpress.org
[mailto:theme-reviewers-bounces@lists.wordpress.org] <b>Im Auftrag von </b>Edward
Caissie<br>
<b>Gesendet:</b> Montag, 13. September 2010 00:51<br>
<b>An:</b> theme-reviewers@lists.wordpress.org<br>
<b>Betreff:</b> Re: [theme-reviewers] My First Suggest-Approval *sniff*<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>I cannot agree more with Chip
on these points, especially in cases where the "new" function
replacing the "deprecated" function is simply a find and replace
process then what is the issue with making it a requirement to use the current
correct function?<br>
<br>
I would be willing to accept a short time line of one or two major releases
with __specific__ exceptions noted explicitly by the __core__ devs otherwise a 30
day grace period from the release date of the current version is fair (provided
the queue does not exceed that same period).<br>
<br>
<br>
Cais.<o:p></o:p></p>
<div>
<p class=MsoNormal>On Sun, Sep 12, 2010 at 6:23 PM, Chip Bennett <<a
href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal>On Sun, Sep 12, 2010 at 5:16 PM, Andrew Nacin <<a
href="mailto:wp@andrewnacin.com" target="_blank">wp@andrewnacin.com</a>>
wrote<o:p></o:p></p>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm'>
<div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On
the other hand, if the theme uses clean_url() instead of esc_url() (as but one
example), please don't reject that theme. I'm just glad they're sanitizing
their outputs.</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</blockquote>
</div>
<div>
<p class=MsoNormal>If someone from the core team or Automattic want to
volunteer to maintain the allowable deprecated function call list from release
to release, and keep the Theme Review Guidelines updated accordingly (i.e. listing
every allowable deprecated function), then perhaps we can consider revising the
current guideline. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Otherwise, I'm not going to commit to reviewing each
deprecated function call ad hoc, and assess whether or not its allowable.
That's just not efficient or effective use of Theme reviewers' time.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:#888888'>Chip<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>