That sounds like a very succinct solution! I'll add that in. Would that remain ambiguous for anyone?<div><br></div><div>Thanks,<br><div><br></div><div>Chip<br><br><div class="gmail_quote">On Thu, Aug 23, 2012 at 11:05 AM, Doug Stewart <span dir="ltr"><<a href="mailto:zamoose@gmail.com" target="_blank">zamoose@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Chip:<br>
Add one word to enhance clarity: "prior". I think that's the<br>
falling-down part. So it becomes "Themes must not support backward<br>
compatibility for more than two PRIOR major WordPress versions". This<br>
excludes the CURRENT version explicitly from "backwards<br>
compatibility".<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Aug 23, 2012 at 11:56 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> The reason to leave in the "relativity" of the version is to ensure that the<br>
> standard remains the same. If through oversight the guidelines aren't<br>
> updated in a timely manner when 3.5 comes out, the guidelines remain<br>
> explicit regarding acceptable degree of backward compatibility. The reason<br>
> for the current "must not"/"shall not" criticality is intentional, since the<br>
> best-practice/recommended degree of backward compatibility is *none*.<br>
><br>
> Here is the current wording:<br>
><br>
> Themes must not support backward compatibility for more than two major<br>
> WordPress versions (currently, that means versions prior to WordPress 3.2)<br>
> Themes should not support backward compatibility for more than one major<br>
> WordPress version (currently, that means versions prior to WordPress 3.3)<br>
><br>
> Would something like this be more clear?<br>
><br>
> Themes must not support backward compatibility for more than two major<br>
> WordPress versions (currently, that means Themes may support backward<br>
> compatibility for WordPress versions 3.3 and 3.2, but must not support<br>
> backward compatibility for WordPress version 3.1 or older)<br>
> Themes should not support backward compatibility for more than one major<br>
> WordPress version (currently, that means Themes should not support backward<br>
> compatibility for WordPress versions 3.2 or older)<br>
><br>
> Though I hesitate to get so...wordy.<br>
><br>
> Chip<br>
><br>
> On Thu, Aug 23, 2012 at 10:40 AM, Edward Caissie <<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>><br>
> wrote:<br>
>><br>
>> I'm actually proposing something much more simpler:<br>
>><br>
>><br>
>>> The oldest version that may be currently supported is 3.2; although it is<br>
>>> strongly recommended the oldest version currently supported be 3.3.<br>
>><br>
>><br>
>> Leave out the relativity of the version ... just simply state what the<br>
>> versions are.<br>
>><br>
>><br>
>> Cais.<br>
>><br>
>><br>
>> On Thu, Aug 23, 2012 at 11:34 AM, Tom Barrett <<a href="mailto:tcbarrett@gmail.com">tcbarrett@gmail.com</a>> wrote:<br>
>>><br>
>>> Hi folks<br>
>>><br>
>>> I personally find the previous and current wording ambiguous/unclear. Too<br>
>>> many negatives and easily taking out of context. Apologies for stirring<br>
>>> things up, but would this wording help (be acceptable):<br>
>>><br>
>>> - Themes must not provide backward compatibility for out-of-date versions<br>
>>> of WordPress.<br>
>>> = This includes the use of conditional function_exists() wrappers.<br>
>>> = Versions are considered out of date if they are 3 versions (or more)<br>
>>> behind the current version. The current version is 3.4 which means version<br>
>>> 3.1 is out of date.<br>
>>> - Theme should not support backward compatibility for the version which<br>
>>> will become out of date with the next release. Avoid supporting version 3.2<br>
>>> as it will soon become out of date.<br>
>>><br>
>>> It's easier to track back the meaning of the words?<br>
>>><br>
>>> Tom<br>
>>><br>
>>> --<br>
>>> <a href="http://www.tcbarrett.com" target="_blank">http://www.tcbarrett.com</a> | <a href="http://gplus.to/tcbarrett" target="_blank">http://gplus.to/tcbarrett</a> |<br>
>>> <a href="http://twitter.com/tcbarrett" target="_blank">http://twitter.com/tcbarrett</a><br>
>>><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><br>
>>><br>
>><br>
>><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><br>
>><br>
><br>
><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><br>
><br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
-Doug<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div></div>