[theme-reviewers] Please make my theme live

[Edward Caissie]

Not a bad idea, but what would you suggest as a guideline for assigning
these tags / flags to insure a consistent approach to using them?

As another idea, we could look at adopting "Semantic Versioning" as a
guideline (see http://semver.org/) ; then use the version number as the
flag, but that again requires a person (the theme author mostly) to
properly version their works; but it will also add to the review
guidelines, to insure the theme author did properly (re-)version their
theme ... hmm, this slope is starting to get a bit slippery ...


Cais.


On Thu, Jun 14, 2012 at 9:07 AM, Doug Stewart <zamoose at gmail.com> wrote:

> On Thu, Jun 14, 2012 at 12:46 AM, Emil Uzelac <emil at themeid.com> wrote:
> > Hi,
> >
> > IMO ticket is a ticket, doesn't matter how big or small the changes are.
> And
> > If we do this that would be the only thing one of us will be doing all
> day
> > long, if you know what I mean.
> >
> > At the present time this is still manual operation. We can do this in
> > "bulk", meaning that every week one would sit down and push bunch of
> > approved Themes into extend and it's still one by one approval.
> >
> > Please see all other response from Otto if you can :)
> >
>
>
> What if there were a way of flagging tickets as "simple" or "bugfix"
> or "security-fix", etc.? Then, any theme approval marked with those
> tags by a reviewer could be automatically swept up in a cron'd wget
> request or similar. This would leave bigger changes to the theme
> admins for review, making everyone's lives easier.
>
> --
> -Doug
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120614/cd84e1b1/attachment.htm>