With Drupal 8 less than a year away, and almost as many users of Ubercart 7.x-3.x as 6.x-2.x, it seems like a good time to stop adding new features to 6.x-2.x and instead encourage users to upgrade.

Bug fixes for 6.x-2.x will still be accepted for the foreseeable future, at least until Drupal 6 itself is no longer supported. New features for 6.x-2.x may still be considered if any contributor wishes to supply a patch, but otherwise feature requests should be bumped to 7.x-3.x or closed.

Comments welcome.


TR’s picture

Agreed, and this has essentially been our policy for the past year.

DanZ’s picture


There should also be a way to encourage 6.x-2.x users to upgrade sooner rather than later. Lots of site maintainers don't know that D6 will be unsupported soon. Maybe something in the Status report? Maybe that's a Drupal problem, not an Ubercart problem?

I've read that the 6.x-2.x -> 7.x-3.x transition can be bumpy. Is there an up-to-date doc on how to do this? (I wouldn't know, as I went straight to D7).

DanZ’s picture

There should also be a way to encourage 6.x-2.x users to upgrade sooner rather than later.

Well, there's one obvious way to do that.

There should be a note on the project page that no new features will be added to 6.x-2.x, only bug fixes.

There should also be a note to encourage admins to do all their new installs in 7.x-3.x.

While you're there, the bit about feature requests not going in this queue should probably be removed.

longwave’s picture

Status: Active » Fixed

The 6 to 7 upgrade process is very dependent on the combination of contrib modules you have installed. Ubercart mostly handles upgrading itself, but there are so many possible contrib modules that we cannot possibly hope to test them all, we can only react if there is something specific we can help work around in Ubercart and it gets reported here.

Otherwise, I think this can be marked fixed and anyone who requests new features for 6.x can be pointed to this issue.

Status: Fixed » Closed (fixed)

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