Port Drupal.org testing profile to D6

This would actually be quite handy for working on the d.o upgrade sprints. We should consider using Install Profile API while we're at it.

p.s. Although, both myself and aclight have had success running the install profile in D5, then upgrading that site to D6 including both core and contrib -- helps test the DB upgrades, etc. So, this isn't a show-stopper... but it would still be handy.

Not required for the drupal.org upgrade.

i'm working on this now. after spending too many hours trying to get drupal_execute() to do my bidding, i've finally given up and decide to start the conversion to the install profile API.

committed this first effort, which is basically working.

couple of things to resolve:

1. 'Active Project release API compatibility terms' setting isn't being set properly. looks like the we're not able to get the tids from the term name.
2. the install is so huge i had to break it up into steps, as i was getting both memory overflows and PHP timeouts. problem is i initially did it in kind of a lame auto-multistep way using the installer tasks. this needs to be converted to batch api.

also, we should probably convert the taxonomy saving stuff to either be embedded in the node_save()'s if we can, or at the very least leverage install profile api's taxo functions.

oops, forgot to mention that this profile will need the latest project_issue code, and this patch to install profile api: http://drupal.org/node/408040

FYI: Last night I committed #408040: functions for creating nodes so this works if you just use the latest Install Profile API code from DRUPAL-6--2 branch or 6.x-2.x-dev.

I also committed a fix to the profile to use install_goto() instead of drupal_goto(). After that, light testing seems to work about as well as the D5 version does. ;) Thanks, hunmonk!

committed the following, which removes the clunky batch method for the shiny and pretty batch API.

not completely working yet, but the batching stuff is right.

drupal_execute() strikes again... :(

turns out we can't use that function at all if we're using batch API, so it's forced to die.

this will also need to be corrected in project issue generate module.

attached is the conversion of taxonomy stuff to the install profile API -- already committed.

attached fixes some taxonomy bugs introduced in the last round, and finally rids the profile of all remaining drupal_execute()'s -- yay!!!

be sure to get latest project issue before testing, because of #408870: convert generation of comments to use project_issue followup api

already committed.

attached has been committed, and fixes a few remaining bugs with issue status, taxonomy, and update messages.

everything seems to be working well now, except for one thing: the batch api messages aren't getting printed on the finished screen. i suspect that there's no call to get the messages in install.php, but not sure. we may need our own custom step before the final screen to print them if we care.

let's call this done and file anything else as a new issue.

batch messages bug is now at #409010: batch messages not displayed on final screen