I've updated the guidelines as follows:<div><br></div><div><ul style="text-align:left;margin-top:0px;margin-right:0px;margin-bottom:22px;margin-left:16px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px;list-style-type:square;list-style-position:initial;font-family:sans-serif;font-size:13px;line-height:22px;background-color:rgb(255,255,255)">
<li style="text-align:left!important;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px">Themes <b>must not</b> support backward compatibility for more than two major WordPress versions (currently, that means versions prior to WordPress 3.2)</li>
<li style="text-align:left!important;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px">Themes <b>should not</b> support backward compatibility for more than one major WordPress version (currently, that means versions prior to WordPress 3.3)</li>
</ul></div><div>Hopefully that eliminates any and all ambiguity.</div><div><br></div><div>Thanks!</div><div><br></div><div>Chip<br><br><div class="gmail_quote">On Thu, Aug 23, 2012 at 9:14 AM, Drew Clardy <span dir="ltr"><<a href="mailto:dclardy64@gmail.com" target="_blank">dclardy64@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I might be a little crazy here, but I read that completely as Chip is stating it. You must not support more than two major versions back. That is currently 3.2. He states that pretty clearly. If there is any confusion, you could change it like this.<div>
<br></div><div><div class="im">Themes must not support backward compatibility for more than two major<br></div>WordPress versions (currently versions less than WordPress 3.2) </div><div><br></div><div>I think that clears it up pretty easily, and I don't think that can be taken any other way.</div>
<div><br></div><div>Drew Clardy<br><br><div class="gmail_quote">On Thu, Aug 23, 2012 at 9:08 AM, <span dir="ltr"><<a href="mailto:theme-reviewers-request@lists.wordpress.org" target="_blank">theme-reviewers-request@lists.wordpress.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send theme-reviewers mailing list submissions to<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:theme-reviewers-request@lists.wordpress.org" target="_blank">theme-reviewers-request@lists.wordpress.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:theme-reviewers-owner@lists.wordpress.org" target="_blank">theme-reviewers-owner@lists.wordpress.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of theme-reviewers digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: unable to upload please advice (Chip Bennett)<br>
2. Re: unable to upload please advice (Otto)<br>
3. Re: unable to upload please advice (Chip Bennett)<br>
4. Re: unable to upload please advice (Fong Li Heng)<br>
5. Re: unable to upload please advice (Otto)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 23 Aug 2012 08:43:53 -0500<br>
From: Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>><div class="im"><br>
Subject: Re: [theme-reviewers] unable to upload please advice<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br></div>
Message-ID:<br>
<CAPdLKqfH_CDJ-v=<a href="mailto:d0PchuROvzm7v-EXvJfiGxmOCepjKiFipag@mail.gmail.com" target="_blank">d0PchuROvzm7v-EXvJfiGxmOCepjKiFipag@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<div class="im"><br>
<br>
That is stating the allowed version to which backward compatibility is<br>
allowed; it clearly indicates what "two prior versions" means.<br>
<br></div><div class="im">
It doesn't make any sense for version 3.4 to be "one prior version to<br>
version 3.4"; thus, it makes no sense for version 3.3 to be "two prior<br>
versions to 3.4".<br>
<br>
Is it seriously unclear? How would you prefer for it to be stated?<br>
<br>
Chip<br>
<br>
On Thu, Aug 23, 2012 at 8:36 AM, Otto <<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>> wrote:<br>
<br></div><div class="im">
> On Thu, Aug 23, 2012 at 8:34 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>><br>
> wrote:<br>
> > In fact, the current guidelines even explicitly indicate the versions for<br>
> > which backward compatibility is allowed:<br>
><br>
> Yes, they do. Exactly. And did you *read* those versions?<br>
><br></div><div class="im">
> > Themes must not support backward compatibility for more than two major<br>
> > WordPress versions (currently: WordPress 3.2)<br>
><br></div><div class="im">
> MUST NOT SUPPORT 3.2. It says it right there, black and white.<br>
><br>
> I'm not sure how it could be any more clear than that, indeed.<br>
><br></div><div class="im">
> -Otto<br>
> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></div>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120823/58e0a1f9/attachment-0001.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120823/58e0a1f9/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 23 Aug 2012 08:50:26 -0500<br>
From: Otto <<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>><div class="im"><br>
Subject: Re: [theme-reviewers] unable to upload please advice<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br></div>
Message-ID:<br>
<<a href="mailto:CAD-FghxUxhc2S1e-V1Wp8qTTLX3gaxWDD53VtQGr4O8JGO4RGw@mail.gmail.com" target="_blank">CAD-FghxUxhc2S1e-V1Wp8qTTLX3gaxWDD53VtQGr4O8JGO4RGw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<div class="im"><br>
<br>
On Thu, Aug 23, 2012 at 8:43 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
> That is stating the allowed version to which backward compatibility is<br>
> allowed; it clearly indicates what "two prior versions" means.<br>
<br>
It has the phrase "must not support" and a version in it, but you're<br>
telling me that the version given is actually allowed to be supported.<br>
<br>
How is that in any way clear, at all?<br>
<br>
I don't know how you should fix it, because apparently I have no idea<br>
what the guideline actually is.. As I read that, right now, even with<br>
your explanation, then I'm reading that theme authors must not support<br>
WordPress 3.2 or earlier. I don't see how anybody could read that<br>
guideline any differently. It's perfectly clear as it is now: No<br>
supporting 3.2 or earlier.<br>
<br>
If you want to change it to make WordPress 3.2 capable of being<br>
supported, which that guideline explicitly says it cannot be, then you<br>
should change it to say that WordPress 3.2 *is* capable of being<br>
supported. How you do that, I have no idea. I would suggest changing<br>
it to not say what it currently says, but what you change it to<br>
depends on what you think it is supposed to say. Which, again, I have<br>
no idea how you could read it any differently from the way I'm reading<br>
it right now.<br>
<br>
-Otto<br>
<br>
<br></div>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 23 Aug 2012 09:01:27 -0500<br>
From: Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>><div class="im"><br>
Subject: Re: [theme-reviewers] unable to upload please advice<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br></div>
Message-ID:<br>
<CAPdLKqeCrh_B_u0=<a href="mailto:DnrhbfVSjpz_TiKOGr9aUCMQ8jybMRAmzA@mail.gmail.com" target="_blank">DnrhbfVSjpz_TiKOGr9aUCMQ8jybMRAmzA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<div class="im"><br>
<br>
Okay, this is pretty straight-forward.<br>
<br></div><div class="im">
The current version is 3.4<br>
One version prior to current is 3.3<br>
Two versions prior to current is 3.2<br>
*More than* one version prior to current is 3.2<br>
*More than* two versions prior to current is 3.1.<br>
<br></div>
The guideline states: "Themes *must not* support backward compatibility *for<br>
more than two major WordPress versions* (currently: WordPress 3.2)"<div class="im"><br>
<br>
There is no possible, logical way that you can conclude that version 3.2 is<br>
MORE THAN TWO versions prior to the current version, which is 3.4.<br>
<br>
Chip<br>
<br>
On Thu, Aug 23, 2012 at 8:50 AM, Otto <<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>> wrote:<br>
<br></div><div class="im">
> On Thu, Aug 23, 2012 at 8:43 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>><br>
> wrote:<br>
> > That is stating the allowed version to which backward compatibility is<br>
> > allowed; it clearly indicates what "two prior versions" means.<br>
><br>
> It has the phrase "must not support" and a version in it, but you're<br>
> telling me that the version given is actually allowed to be supported.<br>
><br>
> How is that in any way clear, at all?<br>
><br>
> I don't know how you should fix it, because apparently I have no idea<br>
> what the guideline actually is.. As I read that, right now, even with<br>
> your explanation, then I'm reading that theme authors must not support<br>
> WordPress 3.2 or earlier. I don't see how anybody could read that<br>
> guideline any differently. It's perfectly clear as it is now: No<br>
> supporting 3.2 or earlier.<br>
><br>
> If you want to change it to make WordPress 3.2 capable of being<br>
> supported, which that guideline explicitly says it cannot be, then you<br>
> should change it to say that WordPress 3.2 *is* capable of being<br>
> supported. How you do that, I have no idea. I would suggest changing<br>
> it to not say what it currently says, but what you change it to<br>
> depends on what you think it is supposed to say. Which, again, I have<br>
> no idea how you could read it any differently from the way I'm reading<br>
> it right now.<br>
><br></div><div class="im">
> -Otto<br>
> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></div>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120823/77f69e3d/attachment-0001.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120823/77f69e3d/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 23 Aug 2012 22:01:32 +0800<br>
From: Fong Li Heng <<a href="mailto:fonglh@gmail.com" target="_blank">fonglh@gmail.com</a>><div class="im"><br>
Subject: Re: [theme-reviewers] unable to upload please advice<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br></div>
Message-ID:<br>
<<a href="mailto:CACCsp-svCrdeM4hf4_3aX6Ek-mpCuoDyw9VHv9OUQzE-Jb4YBw@mail.gmail.com" target="_blank">CACCsp-svCrdeM4hf4_3aX6Ek-mpCuoDyw9VHv9OUQzE-Jb4YBw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<div class="im"><br>
<br>
The 'more than' is important. Versions 'more than' (older than) the stated<br>
one must not be supported. So the stated version is actually allowed as the<br>
phrasing means 'older than' as compared to 'older than or equal to'.<br>
<br>
That's how I interpret it anyway.<br>
<br>
On Thu, Aug 23, 2012 at 9:50 PM, Otto <<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>> wrote:<br>
<br></div><div class="im">
> On Thu, Aug 23, 2012 at 8:43 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>><br>
> wrote:<br>
> > That is stating the allowed version to which backward compatibility is<br>
> > allowed; it clearly indicates what "two prior versions" means.<br>
><br>
> It has the phrase "must not support" and a version in it, but you're<br>
> telling me that the version given is actually allowed to be supported.<br>
><br>
> How is that in any way clear, at all?<br>
><br>
> I don't know how you should fix it, because apparently I have no idea<br>
> what the guideline actually is.. As I read that, right now, even with<br>
> your explanation, then I'm reading that theme authors must not support<br>
> WordPress 3.2 or earlier. I don't see how anybody could read that<br>
> guideline any differently. It's perfectly clear as it is now: No<br>
> supporting 3.2 or earlier.<br>
><br>
> If you want to change it to make WordPress 3.2 capable of being<br>
> supported, which that guideline explicitly says it cannot be, then you<br>
> should change it to say that WordPress 3.2 *is* capable of being<br>
> supported. How you do that, I have no idea. I would suggest changing<br>
> it to not say what it currently says, but what you change it to<br>
> depends on what you think it is supposed to say. Which, again, I have<br>
> no idea how you could read it any differently from the way I'm reading<br>
> it right now.<br>
><br></div><div class="im">
> -Otto<br>
> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></div>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120823/d49f23fa/attachment-0001.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120823/d49f23fa/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Thu, 23 Aug 2012 09:08:09 -0500<br>
From: Otto <<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>><div class="im"><br>
Subject: Re: [theme-reviewers] unable to upload please advice<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br></div>
Message-ID:<br>
<<a href="mailto:CAD-Fghw6c_b8G0ASnHWBN8OxiypqpYKzc-ZDXU6Fccd_b89vTQ@mail.gmail.com" target="_blank">CAD-Fghw6c_b8G0ASnHWBN8OxiypqpYKzc-ZDXU6Fccd_b89vTQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<div class="im"><br>
<br>
On Thu, Aug 23, 2012 at 9:01 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
> Okay, this is pretty straight-forward.<br>
<br>
Yes, actually, it is.<br>
<br>
Change the wording of that guideline.<br>
<br>
It's that simple. I'm not changing a darned thing until that guideline<br>
is changed to be more clear than it is right now. You can use all the<br>
logic you want, and try to explain it over and over, and I can even<br>
understand your explanations and that isn't the problem.<br>
<br>
The problem is that the guideline, as written, is totally unclear.<br>
<br>
Right now, theme check and the uploader say that 3.2 is not allowed<br>
because that was (and *still is*) my interpretation of that text in<br>
the guidelines.<br>
<br>
I'm not going to change that until you fix the text of that guideline<br>
to be clear and explicit about what is allowed.<br>
<br>
If I can misinterpret it, then so can others, and apparently I've been<br>
misinterpreting it for almost *2 years*. Seriously, you just turned<br>
the world upside down on me here, because I've been operating with a<br>
"2 versions of support" notion in my head ever since theme-check was<br>
created, and now you're telling me that we actually allow THREE<br>
versions of support.<br>
<br>
I don't care how you change that text, but it must change. Everything<br>
happening with theme-check *stops* until you do.<br>
<br>
-Otto<br>
<br>
<br></div>
------------------------------<div class="im"><br>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></div>
End of theme-reviewers Digest, Vol 27, Issue 90<br>
***********************************************<br>
</blockquote></div><br></div>
<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></blockquote></div><br></div>