Since the last commit in this module was in july 2014, would it be a problem to tag this latest commit as the hopefully final version 7.x-2.3 , so that the module doesn't remain flagged as recommending the older and more broken 2.2 version on the admin/reports/updates screen ?

Or even better, after adding the currently RTBC patch about the version check in info files.

The release notes could mention this is not an ideal release, but that it has been produced as final because there will not be any more work beyond security issue fixes if any is needed. Maybe even suggesting the move to a Composer workflow ?

Comments

fgm created an issue. See original summary.

darren oh’s picture

darren oh
Primary language English
Location Lakeland, Florida
commented
Status: Active » Closed (duplicate)
Related issues: +#3103990: [D7] Fix dev release time

Running a dev version is not a problem if Drupal recognizes that it is up to date. The patch in #3103990-3: [D7] Fix dev release time will properly support dev releases. Please test and review.