[theme-reviewers] Why can't theme authors have a second version of a theme?

Philip Arthur Moore philip at pressbuild.com
Sat Sep 27 04:30:06 UTC 2014

> Again, we're not trying to pull one over on anyone, we're trying to do what
> makes the most sense for protecting end-user.

Simple solution: upgrade V1 to V2 while also maintaining backwards
compatibility. This can be achieved in any number of ways, but the
primary point is that V1 users are given an opportunity to switch over
to V2 without breaking anything until they are ready to upgrade to the
new markup.

Long term, the best thing for you to think about is Responsive as
Responsive. Not a version number. Who's to say the same issue won't
happen 1 year from now when you've decided to release Responsive III
into the repo?

Unfortunately you have chosen a development road that is in
disagreement with the guidelines of the repo. You should either a)
change the name or b) provide a legit upgrade path for users while
maintaining backwards compatibility.

It shouldn't matter how much time you've already put into this. Wrong
is wrong. Things have been pulled from Core just before release that
have taken hundreds of man hours because they were wrong.

I don't like typing because sometimes my tone can come across as
harsh, so please don't take it that way. It's just somewhat annoying
that this is even a conversation, when the main reason this is an
issue is because the term Responsive is valuable to your business,
which has absolutely nothing to do with maintaing proper development
practices for WordPress, themes, and the repo.

More information about the theme-reviewers mailing list