It is my opinion that we should not continue support and development of this branch. Any and all improvements to xmlsitemap should happen only in the 6.x branches and only bug fixes applied to 5.x-1.x-dev. Comments?

Comments

mr.j’s picture

That's a shame for all us drupal 5 users.

dave reid’s picture

I agree with earnie that we should essentially close all Drupal 5 branches to any kind of feature requests and only bug fixes should be backported if possible. Even then it should only be critical bug fixes (the only kind of fixes accepted for Drupal 5 core now). The 5.x-1.x branch is probably the best-working Drupal 5 version of the module.

@mr.j: We now only have two maintainers for a fairly large module. Drupal 6 has been released for over two years and at least for myself, I no longer use Drupal 5 in any way, shape or form. Backporting changes to the Drupal 5 branch at this point is frustrating and most often difficult to do without the improved APIs provided by Drupal 6. If fellow Drupal 5 users are able to create patches and other users can review those patches, that helps us out immensely.

avpaderno’s picture

Title: Close the 5.x-2.x-dev branch as unsupported. » Close the 5.x-2.x-dev branch as unsupported

To notice that the batch API has been ported to Drupal 5 via a third-party module.

tetramentis’s picture

I guess it is time to upgrade to D6, then :)

Anonymous’s picture

Status: Active » Fixed

This task has been completed.

sashomi’s picture

I'm sorry to hear this, because I need this 2.x branch for Drupal 5.x. My site is using i18n and ubercart, and it will be difficult to upgrade all this and all other modules in Drupal 6. The 1.6 version of XML Sitemap does not supoort i18n, so it's useless for me.

dave reid’s picture

@sashomi: We never said you have to stop using it. Keep using it all you want. We just are not able to support that version anymore. When you're ready to upgrade to Drupal 6 (which both i18n and ubercart have great 6.x versions available), we will have fully supported and great working versions for you. It is not worth the little free time we have to devote to this project to support a Drupal version that neither of us maintainers use regularly.

sashomi’s picture

ok, thanks for this quick reply. Unfortunately I won't migrate soon to Drupal 6, for I have lots of custom modules and theme and everything is working great and I have no motive to move to 6, except it's new. Maybe soon when other maintainers stop supporting their modules, I'll be forced to do it :) But that's my problem. Thanks again for your work.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.