[wp-hackers] WP 3.1 admin bar

Kim Parsell kparsell-wp at kpdesign.net
Fri Feb 18 04:29:58 UTC 2011

This isn't about the length of time it would take for someone to do what 
you think should be done, it's about sticking with project release protocol.

Once a release reaches RC status, it is too late to do this. RC = bug 
fixes, not tweaks, and this isn't a bug.

While I understand that you aren't happy about it being on by default, 
it is way past time to do anything about it for 3.1.

There have been plenty of suggestions in this thread on how to disable 
it for your clients' installs, so you can pick which one would be the 
easiest for you to implement.

So, rather than arguing the merits of on/off, perhaps you should be 
looking at notifying your clients of what's coming and gather their 
feedback on whether they want it or not.

Peace out.



Mark E wrote:
> On 02/17/2011 03:06 PM, Jane Wells wrote:
>> Exactly. Anyone whose business is built on or even remotely near
>> WordPress should at the very least be subscribed to
>> http://wpdevel.wordpress.com so that even if you don't get involved in
>> the scheduled (and open) core development chats, you at least know
>> what's going on before it is too late to have an effect (or at least too
>> late to have a positive effect).
> I think ace coder slingers are acutely aware of how long it'd take to 
> tweak this feature to be off by default for existing installs... So 
> insinuating that it's too late for change before 3.1 releases is not 
> based in any actually tweak time time considerations.
> Mark
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list