Project issue 5.x-2.0 release worksheet

Events happening in the community are now at Drupal community events on www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!
Posted by hunmonk on January 15, 2008 at 4:30pm
Last updated by dww on Thu, 2008-02-07 18:13

Following is a worksheet of necessary items to complete in order to get Project issue 5.x-2.0 out the door:

Update: Now released: project_issue 5.x-2.0

Bugs:

  • http://drupal.org/node/210256 -- auto closer broken when anon can't access issues Fixed on 2008-01-16
  • http://drupal.org/node/89673 -- project issue to link filter, causing segfaults on d.o Fixed on 2008-02-04
  • http://drupal.org/node/196478 -- changes to project don't appear when previewing a comment Fixed on 2008-01-21

Low-hanging fruit (none of this has to be done, but a lot of them look pretty easy):

  • http://drupal.org/node/200097 -- Remove duplicate code for issue attribute labels Fixed on 2008-01-19
  • http://drupal.org/node/162760 -- add pager/tablesorting to project/issues/statistics Fixed on 2008-01-20
  • http://drupal.org/node/138054 -- Include comment numbers for issues in email Fixed on 2008-01-21
  • http://drupal.org/node/151984 -- display the initial issue metadata with the initial issue post (This might be easy thanks to the schema used with IFAC, right?) by chad: displaying the data would be easy, but deciding the layout is going to require some discussion, and probably some alteration of the existing design of the page, so i think this is out of scope for 2.0

Comments

issue filter not a blocker?

Posted by dww on January 15, 2008 at 6:55pm
dww's picture

I'm not convinced http://drupal.org/node/89673 belongs on this list. Yes, it's a cool feature, but I don't think it's essential to hold up the 5.x-2.0 release for it.

not to mention

Posted by hunmonk on January 16, 2008 at 3:14pm
hunmonk's picture

that we simply can't repro the segfaulting bug anywhere but d.o, so at the moment it's a d.o specific bug :(

but, if it really is a problem w/ excessive memory usage by the filter, it would be nice to fix that in the code before a release. i'm leaving it in the list for now, but i agree that if only d.o continues to mystify us in this regard, that it shouldn't hold up the release.

Oh right, I forgot we already committed it. ;)

Posted by dww on January 16, 2008 at 5:34pm
dww's picture

Oh yeah, it's already in the code. If it really doesn't work in general, then we should either (temporarily) remove it before the release, or fix it. Thanks for the reminder.

it does work, just fine

Posted by hunmonk on January 16, 2008 at 5:55pm
hunmonk's picture

except on the cursed d.o website :(

Issue tracking and software releases

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: