Port availability calendars to D7

No work is currently underway on this, partially because there are a number of changes getting tightened up in the current module. Once those changes are complete and we have released a new release with the features that have been getting worked out then i will look into porting it.

Started to work on a port.

Please find attached the D7 port. Give it a try and report all your findings here.

WARNING: Do not test on an upgrade, only on a new install!
The patch for #306461: Custom availability states and legend comment #66 (http://drupal.org/node/306461#comment-4068690) is part of this port and so this port needs the availability_calendars_update_6104() to be run for existing installs. I'm not sure whether hook_update_N() for older major Drupal versions will be run. Also, the hook_update_N() functions before 6104 are not (yet) converted.

Notes:

• translation files are no longer part of module distributions. We should assure that the ones that were part of the distribution are fully available on localize.drupal.org.
• all $Id's have been removed form this port, the great git migration did so.
• I added a CHANGELOG.txt to document the changes, see that file for more details.

To be decided:

• Keep hook_update_N() functions 6101, 6102 and 6103? Or do we say first upgrade to 6.x-1.5 before upgrading to D7? (I favour removing them)
• Will #306461: Custom availability states and legend be committed to D6, or do we renumber hook_update_N() function 6104 to 7100/7200?
• Looking at the architectural changes, will this be version 2.0 or 1.6?
• I can post a patch for #1060214: Prepare for D7 port. This will ease the task of back porting future changes in the D7 version to the D6 version. Are people interested in this?
• The location of the admin settings page in the menu: is this the correct place? There are not many pages anymore on this level, most are 1 deeper (under regional settings, content creation, development, etc.). Still, the conversion page told me this was the way to go.

TODO:

• me: test the upgrade path
• you: test and (code) review the port on a new install and report all your findings.

feitserwin, are you interested in becoming a co-maintainer for the D7 and/or the D6 branch. I would enjoy having the assistance.

Yes, please. At least for the D7 branch and issue fixing D6. Note that back porting can be made easier with #1060214: Prepare for D7 port, that's why I created a separate issue for that.

I am working on getting you access.

Just committed the D7 port to the 7.x-2.x branch. The download should show up on the project page soon. This version is functionally equivalent to the 6.x-2.x branch and that will remain so until we officially release 6.x-2.0 respectively 7.x-2.0. After that we strive to keep these versions in sync. To ease the task of forward/back porting, the differences between the initial D6 and D7 2.0 version are kept to a minimum. Still, this will cost a lot of time. So any help in back/forward porting patches/features will be more than welcome.

pcsupport, you can always help by simply testing the newest version and reporting issues, thanks for your concern.