[wp-testers] WordPress 2.0.6 Beta 1

[Brian Layman]

Thanks Mark!  That looks much better.  But I do have a couple of
questions...
Even though these two are marked as duplicates:
Ticket #3415 Update "no wp-config.php" help link - The page this error
linked to no longer existed on WordPress.Org.  The link has been fixed.
Ticket #3390 Better get_page_uri - This is mainly an optimization for pages
that display complete page heirarchies / navigation menus.  The DB is
accessed once rather than many times.

Aren't they both things that we would want to have in 2.0.6?  Especially
3390 as WP 2.0 is now part of the (what was it?) Debian distro?  I don't see
any other ticket tying this issue back to 2.0.6/

May I ask how did you determine this range "&rev=4620&stop_rev=4470".  Did
you have a reference to this somewhere or is this just something you knew
based upon familiarity?  (I'll figure out, later, what "Stop on copy" does
unless you want to explain that quickly too.)

I'm used to now working in an environment where no code change is made
without being tied to a ticket.  It seems that is a bad assumption for
WordPress.  Is this statement true: "The Trac Ticket report will not fully
describe the feature set for each new release.  To get a complete feature
set, you have to review the description and content of each patch applied to
that release's branch.  There is no summary report of all of the changes and
why they occurred."?

Anyway, thanks for your time. I really need to dig up Owen's (Ryan's?) post
on how to make patches.  I've never had the time to lookup how to make those
diffs, but its probably quicker to make the code changes than to explain
some issues in full detail...  Matt and Ryan keep asking us to make changes,
but without that final bit of info, I've no way of attaching my stuff to
tickets...
_______________________________________________
Brian Layman
www.TheCodeCave.com