I just want to point out that four people won't ever be able to fix all
of those tickets. Luckily there are many kick ass people helping out.
My only advice is to perhaps join in, pick a ticket and upload a patch.
Jacob Santos
Charles E. Frees-Melvin wrote:
There are also a significant number of these tickets that are
importers with patches that are almost there but not quite. I think
that we should try with 2.6 or 2.7 to fix and implements all these
importers and on a promotional bandwagan "Come to WP, Install in 5
minutes, and keep your content" also trac should have a dedicated
component "Importers" to trac these tickets.
2008/6/15 Matthew Robinson <[EMAIL PROTECTED]>:
On 15 Jun 2008, at 20:51, Ryan Boren wrote:
Even if another big UI changes after the big 2.5 changes
doesn't sound a nice idea...
Indeed, it does beg the question; why not before/instead of the 2.5
changes?
There's a reason this is being done in a separate branch. It's a
testbed for ideas based on 2.5 feedback and further 2.5 user testing.
Some of the ideas will make it back into trunk. Most probably will
not.
While I fully support the continued development of WordPress can I point out
that there are currently 125 open bug tickets for the 2.5 branch and 795 for
the 2.6 branch.
I'd have to say that I'd much rather some focus went on fixing these bugs
(or closing the invalid tickets) before much coding energy was spent on
tinkering with the UI.
Matt
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
