http://drupal.org/node/1999616

I'm not sure if this was related to #2000290: Please delete the 1.x release of CiviCRM Starter Kit. Probably not, but after the 1.x release was deleted the -rcX tags started showing up as "packagable" releases again. When they weren't available, I created 3.3. But now it looks like 3.3 trumps both the newer 3.3-rc4 (which makes perfect sense) and 3.4-rc2 (which makes less sense).

Ideally, 3.3-rc4 would be showing up on the project page. That is what we're pushing to Pantheon.

Comments

kreynen’s picture

kreynen commented
Priority: Normal » Major

Now this is security issue since the 3.3 release includes Webform 3.18. That the 3.3 release "goes green" when I updated webform in 3.3-rc6 is really confusing. 3.3 has a known security issue, but is being presented to users as if all of the modules are secure.

Please delete the 3.3 release.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Once you have a "7.x-3.0" the project page will never show a "7.x-3.D-anything" It doesn't matter if the D is higher than zero, if there's anything after the D position then it is considered an unstable release that should not be on the project page. There was a lot of discussion about that in ~2009 when the packaging system was created and...this was the decision. I think the logic is that most users should not be prompted to upgrade from 7.x-3.0 to an rc or beta.

If you want a beta/RC cycle you have to jump to 7.x-4.0-rc or just live with the idea of a link from the project page itself.

I agree that it's a bug that 7.x-3.3 is shown in green and I'm not sure why that is.

If you want the project page to show the latest code, I suggest you create a 7.x-3.4 based on the 7.x-3.3-rc code. It's very unlikely that the code to determine which release to show on a project page will be changed in the near future.

dddave’s picture

dddave commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Time has sort of fixed this issue.