No Meetup Tomorrow
If everyone wants to meet and hang out, they can, but the US folks (hi) will be off eating turkey. 
For next week, since 3.5 RC should be coming out soon, everyone should think about putting the RCs on their site and helping us test 
After all, you’re support! You gotta know what’s coming. Also I’ll be putting up the OMGWTFBBQ! post for review, and suggestions, early next week, and I’d love it if everyone came up with a list of weird things in 3.5.
Oh and don’t forget to update your plugin readmes with ‘compatible up to…’ if they are.
Ipstenu (Mika Epstein) 12:06 am on November 22, 2012 Permalink |
See also: http://make.wordpress.org/core/2012/11/21/the-short-road-to-3-5/
esmi 4:29 pm on November 22, 2012 Permalink |
I think we should push for a similar “compatible with” for themes – especially since there’s no mandatory obligation to support older versions of WP in the theme review guidelines. I seem to have seen quite a few forum topics where people with old versions of WP are installing new themes. wp_get_theme() seems to be the real killer.
Ipstenu (Mika Epstein) 4:30 pm on November 22, 2012 Permalink |
If it was as easy to update that in themes ( @chipbennett is it? ) I would, but IIRC you can’t just edit the readme like you can with plugins.
Chip Bennett 3:13 pm on November 23, 2012 Permalink |
No, it’s not. The infrastructure is entirely different. I’d love to see a way to update Theme metadata easily (such as compatible-up-to/tested-up-to/requires), but how to implement something like that would be a question for @otto42
esmi 5:43 pm on November 23, 2012 Permalink |
Maybe we could persuade him to add something to the theme template tags – maybe something along the lines of Min WP Version? There’s already something very similar being used for child themes to indicate the appropriate version of the parent theme.