project overview pages when using the project taxonomy.  We need to
restrict to top-level terms so that if any 2nd-level terms happen to
have the same name, there's no collision and non-deterministic behavior.

that caused it to restrict access to nodes it should have allowed.

category overview page with term descriptions.

It was buggy, too (there was no link) so there's no visible change.

using the "Project type" vocabulary when adding or editing project
nodes.  The code didn't work, so it wasn't displaying anyway, and the
UI has been so majorly improved (#64221) that the help isn't needed.

the project vocabulary on the settings page. The text is now displayed
at admin/content/taxonomy if you view the "Project type" vocabulary.

Backporting isn't technically necessary, since the bug doesn't appear
in 4.7.x, but the extra div can't hurt.

Backported by dww for DRUPAL-4-7.

messages" and "Developers" pages, along with a better version of
project_project_set_breadcrumb() to make it easier to get breadcrumbs
right in other places in the project* codebase.

project has no repository set.

taxonomy terms that don't belong to the "Projects" vocabulary, and
the links don't include other goodness from taxonomy_link(), for
example, mouse-over link titles for term descriptions, etc.

Thanks to merlinofchaos for helping to find the bug in the count_query SQL.

i was foolishly not breaking out of the $op cases.  so, 'view' was
falling through and hitting the 'create' case and returning FALSE.

delete rights to individual projects due to project_access() bug.

checkboxes to be inline'ed on project node forms.

- removing some stray whitespace and a line of commented-out dead code.

hook_form() which was added in revision 1.15, 2003. ;) moshe was the
author and can't now remember what it's for: "dunno. delete it."

i missed when backporting this fix to DRUPAL-4-7. :(  This causes
undefined function errors when you try to add a release in 4.7.x-1.*.