Closed (won't fix)
Project:
Read More Link (Drupal 6 and earlier)
Version:
6.x-4.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Feb 2009 at 10:01 UTC
Updated:
6 Feb 2009 at 05:10 UTC
Available Updates reports that 6.x-4.0 is installed but no longer supported but then points to 6.x-4.0 as the recommended version.
Comments
Comment #1
mcurry commentedSorry, I can't fix this, but I will make 4.0 available and supported and recommended and all the other yummy things that should help Drupal 6's update manager happy. Update to 4.0 and be done with it.
Comment #2
dave reidI'm not sure that's an acceptible solution. Are you going to be maintaining both branches at the same time? Making a 3.0 and 4.0 available to download on the project page is just going to continue to confuse users wanting to use this module. Your best option is probably to mark 4.0 as unsupported, do not list the download, and direct everyone to use 3.0 before it gets too widespread (or vice versa). Basically, let's pick one please.
Comment #3
mcurry commentedNo, I won't support both. They aren't branches, they're tags. They are the same code.
Again, I wish I could delete a release, but I can't.
I'll remove the 'supported' flag from the 4.0 release, but if people keep opening bugs against this module due to Drupal 6 nagging, I'll have to ask the Drupal infrastructure support team to step in and help... =)
Comment #4
dave reidHey that's the best you can do. There's really not much more the infrastructure team can do...it's very against policy to delete releases. You can really only remove the supported flag and make it not available to download. Thanks for helping with this module! I'll help keep an eye out for users creating any issues about the 6.x-4.0 and direct them to the correct release.