The project page official release section lists 5.x-1.5 as latest recommended release for 5.x but 5.x-1.5-8 is the last tagged 5.x release as far as I know. See: http://drupal.org/node/118128/release?api_version[]=78

The 5.x-1.5 build I downloaded appears to have a number of issues, including very slow and 'chatty' (log noise) cron handling and lacks the ability to purge ads (this is a known problem, fixed in 5.x-1.5-8). See: http://drupal.org/node/164738

Is there a reason why 5.x-1.5-8 isn't recommended? Which should I use for a production site?

Comments

milesgillham’s picture

milesgillham commented

You've raised a very, very good point. Why indeed? I seem unable to bless 5.x-1.5.8 as the recommended release. Investigating.

Cheers,

Miles

milesgillham’s picture

milesgillham commented
Assigned: Unassigned » milesgillham
Status: Active » Needs review

I had just assumed it was all set up fine and haven't played with 5--1.5-8 because I wasn't progressing that branch. I've started a 5--2.x branch but not released against it yet.

I'm starting to think Drupal CVS finds DRUPAL-5--1-5-8 to be an invalid tag. It prefers the format DRUPAL-5--1-5, anything after that is supposed to be within prescribed formats (http://drupal.org/node/93999). I don't know if this changed at some point after you were initially developing the module. In essence I think you should have been working on the DRUPAL-5--1-5 branch and tagging as something like DRUPAL-5--1-5-ALPHA1 and so forth to the point of tagging finally to DRUPAL-5--1-5.

The fix is simple. I can jump DRUPAL-5--1-5-8 onto the branch DRUPAL-5--1-6 as a re-release and it will work fine. Assuming I understand CVS correctly in a Drupal context.

If no objections or wiser comments that's what I'll do within 24 hours as I quite agree 1.5-8 is superior until the 5-2.0 is released (common codebase with 6.x ad 7.x :-) although I was quite ambitious in estimating the effort to do so :-(

Cheers,

Miles

fgm’s picture

fgm
Primary language French
Location Paris, France
commented
Status: Closed (fixed) » Fixed

Tag 5.1.6 created today for the final 5.x release on the 5.1 branch. Not that, although 5.1.6 is the /final/ release, it is just a snapshot of the last dev version, completely broken.

The best release remains 5.1.5.

Status: Needs review » Closed (fixed)

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

Status: Fixed » Closed (fixed)

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