Personally I just manual edit the $version and go for it ... I wrote a reminder article this morning explaining the 4 simple steps to do it.<br><br><br>Cais.<br><br>PS: Chip, thanks again for the new feature idea with BNS Inline Asides ... I used it for the post's NB! EAC.<br>
<br><div class="gmail_quote">On Thu, May 12, 2011 at 7:35 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Good morning, Theme reviewers and developers!<div><br></div><div><a href="http://wordpress.org/news/2011/05/wordpress-3-2-beta-1/" target="_blank">WordPress 3.2 Beta 1 is upon us</a>.</div><div><br></div><div><b>Reviewers</b>, now is the time to switch your test environments to the beta (e.g. using the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/" target="_blank">WordPress Beta Tester</a> Plugin), and to start identifying any potential changes to the Guidelines based on the 3.2 release. (There shouldn't be many this cycle.)</div>
<div><br></div><div><b>Developers</b>: now is a great time to switch your development environments to the beta (e.g. using the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/" target="_blank">WordPress Beta Tester</a> Plugin), to start working out any issues that might be introduced in the new code.</div>
<div><br></div><div>Cheers!</div><div><br></div><font color="#888888"><div>Chip</div>
</font><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>