New 6.x Releases on the Horizon

So, Freso and I have had some discussion about what bugs should be fixed prior to a 6.x-2 branch and what should go in after. I wanted to do a little more to keep track of this state (and also give people a little advanced warning that a 6.x-1.1 is about to be released so that you can help test it).

Edit 2008, Sep 30: It's that time again - time for 6.x-1.2 and 5.x-2.4 to be released soon since this was a relatively nasty bug that I think was behind a lot of problems that people were having...

If there is a bug that you think should be fixed prior to a 6.x-1.1 feel free to add it to the list.

Issues For Before 6.x-1.1 (i.e. what should be in both branches)

• pgsql compliance and performance improvement for node bulk updates
• "Strings to Remove" not being removed if they are capitals or the first/last word in the box.
• Doxygen clean-up
• Simpletest for Pathauto
• Use drupal_str functions instead of str functions
• Add per-language patterns for multilingual node types
• Individual path is away after opening preview
• Editing customized profile fields deletes blog aliases
• Code (style) normalisation
• If an existing redirect is exactly the same as the current alias, delete the redirect
• Synchronising 5.x-2.x and 6.x-1.x
• bookpathalias token not working
• Update the README.txt and INSTALL.txt

Issues For Before 6.x-1.2

• Bulk Update of Category Path with no existing categories AND/OR remove bulk generate checkbox?
• Fix the automatic alias checkbox on node form

Issues For 6.x-2.x (i.e. what will become the 6.x-2.x branch)

• Use existing transliteration module
• require confirmation before deleting aliases
• allow other modules to affect strings to help with custom accent/string replacement
• perform bulk updates during cron and/or via the batch API
• Create separate bulk update page
• Bulk update the old way (replacing aliases)
• UI Review from devel list
• String clean up
  Actually, I think this could easily be pushed to 2.x as the strings aren't awful and I think the .pot has been stirred quite enough by my double-space cleansing. :) -Freso
• Split some of the code into smaller pieces (== more testable code)
  Will affect or be affected by "allow other modules to affect strings ...", possibly even being swallowed by that issue entirely.
• Allow unique "Update Action" settings per item type (node, taxonomy,etc) or item (eg. page, story, vocabulary, etc) - I'd really like to see this make it in 1.x :) I but 2.x is ok. I'm willing to re-roll the patch when someone is ready to consider it.
• Editing nodes without an alias should create an alias even with update action = 'Do nothing with existing aliases' - I really think this one needs to get committed, as it leads to a situations where the user "asks" for an automatic alias but one isn't generated. Note that it also affects bulk updates, as nodes with empty aliases will never get updated.
  After discussing this, we decided to push this back for 2.x, as old users may have become accustomed to this behaviour, and they shouldn't be surprised with the release of 6.x-1.1. It should definitely be fixed in 6.x-2.x though! -Freso
• More simpletests...

Also, note that when we branch for 6.x-2.x that will probably be the end of active development of the 5.x branch. Beyond that point something will have to be a bug and/or really important to get committed to the 5.x-2.x/6.x-1.x branches.