5.x-2.0-alpha4 mistakenly marked as security release

The update was regarding my implementation of token api and outputting clean data. The latest 2.x releases do not have this issue.

1.1 is completely unaffected.

As for why update module is flagging for the update - i have no idea. Its possibly I pooched something with CVS. I've only recently learned that you're meant to branch from HEAD... In the past I simple checked out the most recently updated old version and re-branched from that branch... Hence my modules tending to have quite long version ID's.

Meant to say 2.x-dev

You are saying for 2.0 alpha 4:
"This is an alpha - so use with extreme caution… Things might/will probably change before official 2.0 release and therefore this is unlikely to be production ready yet…"

2.0 alpha 4 is on the other hand the only 5.x official release stated, and update module also insisted that version 1.1 has a security update and has to be updated.

So, what to use at the production site now?

It would be nice to be a bit more consistent about versions in the future...

Ok - the reason 2.x was flagged as a security update was my mistake - i must have accidentally selected it. On a side note, dev branches should never be able to be a security release anyway. I've removed the security tag from 2.x-dev now.

The 2.x branch is almost ready for a final release - only 1 issue left to address as far as I know (the CCK tokens issue).

If you want to stick with 1.1 then you're more than welcome to...

On the Project releases page (http://drupal.org/node/50516/edit/releases), version 2 was selected as the Major version for 5.x. I've changed it back to version 1 for two reasons:

1. Otherwise 5.x-1.1 won't appear on the project page
2. The default release is always the latest release from the Major version. And it is used as the recommended release in the Update Status module. Which is why everyone was being told to upgrade to 2.0-alpha4.

Ohh I didn't know that.

Thanks John.

Well, don't feel bad, Nick. It's not obvious how the Major version toggle works. I had to play with that toggle on a different project before I realized what it did.