Now that Drupal 6 is out, getting the project* family of modules ported to D6 is going to become an urgent task. We want to ensure that by the time the final release candidates are out, we're ready to upgrade drupal.org to D6 (which must happen before the official 6.0 release is possible). That's going to take a lot of effort, and hunmonk and I have some very specific plans for how it should all happen. This page will be the place to keep track of what has to get done, in what order, so that anyone who wants to help knows where to put their efforts. It's obviously a work-in-progress, so feel free to help keep it updated, add issue links where appropriate, cross off things that are completed, or add other steps that need to happen.
I'm cross-posting this to a lot of groups since: a) converting project* to use views is a big part of this effort (so we have significantly less code to support in project* and port to newer versions of core), b) since we need lots of volunteers/help, and c) in case anyone is able to help sponsor some of this work to ensure that everything is completed well before the core maintainers would like to ship 6.0. Thanks!
#103790, #103791, #103795 and #177271: Make project* E_ALL compliant (since we have to do it eventually, anyway, and it'll be easier to do this before we make more branches, etc). finish up existing project module bugs here: http://tinyurl.com/ynq2n6 and also here: http://groups.drupal.org/node/7396Finished on 2008-01-06 Project: cut a 5.x-1.2 release of everything(finished on 2008-01-06), and finally create the DRUPAL-5 branch. Project issue tracker: Fix issues at http://groups.drupal.org/node/7396, cut a 5.x-1.2 release of everything, and finally create the DRUPAL-5 branch.Finished on 2008-01-06 #18920: Convert issue followups to comments (mostly done, just needs more help with the upgrade path, testing, and more reviews). Project subscriptions or other aspects may benefit from this proposed enhancement to Views: http://drupal.org/node/103171.Note: there is now a module called Views Bulk Operations that makes this patch unnecessary. Test the Version Control API, CVS backend and Project integration version control modules. The release node integration needs to be completed (probably in versioncontrol_project). [This can all happen in parallel with most of the rest of this list, unless we decide it'll be significantly easier to do the release node FAPI integration via D6 FAPI].-- postponed until after d.o is running 6.x, see http://groups.drupal.org/node/8102
Work to do for the actual 6.x ports
#157694: Port project to 6.x #157693: Port project_issue to 6.x #76725: Convert the issue queues into views (project_issue_views.inc) -- I started this for my day job -- however, the goal would be to actually rip out all the existing code and make project_issue require views, which will take a little more work (but remove *tons* of code we'll no longer have to maintain).
- #76726: Convert the project browsing pages into views (project_views.inc)
#209408: Port CVS module to 6.x #225059: test CVS 6.x project components
- Deploy everything on s.d.o
Work to do after the initial 6.x port
Port versioncontrol* to 6.x. Probably sounds like a lot, but it's not much more code than the existing CVS integration module, and it's a) much better code and b) much more flexible for the future, and c) potentially useful to other sites. [Note: this can happen in parallel with project_issue porting].-- postponed until after d.o is running 6.x, see http://groups.drupal.org/node/8102
|Project module upgrade to Drupal 6 for Drupal.org_.png||94.72 KB|