On Thu, Nov 8, 2012 at 3:52 PM, esmi at quirm dot net <span dir="ltr"><<a href="mailto:esmi@quirm.net" target="_blank">esmi@quirm.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just got this question on the support forums and I'm a bit stumped for any firm policy line on how long older default themes will be supported for.<br>
<br>
Anyone come across something on this subject?</blockquote><div><br></div><div>The plan is to continue to maintain the default themes, from Twenty Ten on.</div><div><br></div><div>It's actually quite simple to do, so I don't expect this plan to change in the foreseeable future. Once the default themes each hit 1.0, we don't touch the code much anyway, as we want to avoid breaking child themes (even with regards to styling). So we're mostly just working out bug fixes as they get reported; and opting in to new core features as we go. Adding support for newer core features is an obvious thing to do, because it allows us to eat our own dog food. We can't expect someone else to update a theme to use a new feature, especially in a backwards compatible way, if we can't do it ourselves. But none of the themes are getting rewritten, or anything like that.</div>
<div><br></div><div>Anyway, you can continue to file tickets under the "Bundled Theme" component on Trac. This will be the case even after Twenty Ten becomes "unbundled," which I think might be for 3.5. (From there, we'll continue with a policy of always shipping two themes.)</div>
</div>