#201479 by chx, ximo: forum module requires taxonomy for uninstall but taxonomy might be disabled at that time, so we need to include it

#186546 by bjaspan: fix missing forum vocabulary when people turned on forum module, but never visited any pages in Drupal 5 and they upgrade to Drupal 6 which does this much better

#99947 by neclimdul, Sutharsan, keith.smith: forum module help text and form description update, removing reference to other forum software as well

#193333 follow up by catch: remove reset to alphabetical button shown on forum forms incidentally as a result of the taxonomy drag and drop patch

#200069 by keith.smith: new standard for 'more information' links in module help texts, as the handbook we referred to before was renamed

#197297 by DanW (as GHOP 17), and keith.smith: clean up lots of help texts, update to drag and drop functionality, drupal.module removal, etc

#176282 by Desbeers: forum taxonomy was required for non-forum node types, when enabled for forum inclusion

 - whitespaces at end of lines
 - indentation
 - control structure usage
 - whitespace in empty lines
 - phpdoc comment formatting

#194075 by neclimdul: nodeapi load should return an array by documentation, and forum's nodeapi load returns an object

- Patch #192242 by catch, quicksketch, webchick, keith et all: usability improvements for the vocabulary/term forms.

#177497 by chx and Desbeers: revive Drupal 5's menu_set_location() functionality by introducing menu_set_item() (for consistency in function naming), thus fixing a regression in the current development code. Also fixing some misuse of menu_set_location() by using drupal_set_breadcrumb() instead.

#72487 by chx, pwolanin and moshe weitzman: let node_access() work on arbitrary users, so independent user access checks can be done in a request

#175979 by Desbeers: forum module does not need to call node_prepare anymore, because it is already done

- Patch #180432 by hunmonk, sun, et al: make comment settings per node type.  This is a new feature that slipped in because it is required for the project module on drupal.org.

- Patch #150245 by webchick, bjaspan, ralf, Arancaytar et al: move the .schema files into .install files to prevent mistakes.

#174343 by Shiny: move JOIN condition to ON clause in forum_nodeapi, so our SQL is standards compatible

#6162 by various people: actually point new anchors to the page the first new comment is displayed (in a multipage comment view)

#53905 by fax8, Gurpartap Singh and dvessel: give meaningful names to term variables in forum templates and add unique IDs for easier themeing

#161107 by fwalch and bragon: actually implement the missing forum_term_load to work behind the %forum_term menu item resolving calls

- Patch #168028 by dvessler, merlinofchaos, pwolanin et al: both theme functions and templates may need include files. Flush your caches.

- Patch #163191 by hswong3i: removed db_num_rows() for compatibility with Oracle and DB2.  Also a performance improvement.

 - always include CVS Id tags in all files
 - add a new line after the CVS Id, if more code or phpdoc follows in the same code block
 - fix bogus Id tags previously added

  This is a small form API extension (doesn't break existing code) that
  facilitates the Drupal 6 upgrade of the Views module.  A good example
  of why it can be beneficial to start upgrading your modules early on in
  the code freeze. ;)

- Patch #158536 by dvessel: some more gentle massaging of template files.  Trying to make it easier to discover the different template files.

#100641 by kkaefer, ChrisKennedy and RobRoy: change 'Submit' buttons to 'Save' to compliy with the desktop metaphor and actually tell what the button does ('we know it submits the form, but what it does?')

- Patch #20295 by pyromanfo, webchick, Gurpartap Singh et al: allow forum topics to be custom node types.

  unanimously agreed to rollback the deletion API.  We all support the
  features this patch added, yet not its actual design and implementation.
  After some talk, we decided that it would be better for Drupal -- in the
  long term -- not to go with a solution that isn't 100%. We also recognize
  that in the short term, this patch would have been useful addition. So
  let's figure out how we can implement this properly in D7.