Since the front page recommends installing a beta release, put that release (7.x-1.9-beta5) on the front page as an "Other release" and leave 1.8 up as the "Recommended release".
This would making things easier on those folks who don't know how to use GIT or the repository viewer. It would also allow the whole module update notification system to work.
Note: I've never tried this on my projects with a sub-version. If drupal.org can't do that, maybe it could be called 2.0-beta5 or maybe put up directions on how to use the repository viewer to get the right archive.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | Screen Shot 2013-04-10 at 12.52.36 PM.png | 122.58 KB | pixelsweatshop |
Comments
Comment #1
DanZ commentedFix that title.
Comment #2
mehrpadin commentedHey there,
Thanks, done.
Comment #3
pixelsweatshop commentedThis still hasn't been done.
There still isn't an "other" release on the project page
I was prompted for an update by drush this morning to 1.9 only to find it is not the recommended release, nor an "other" release.
Your project page needs to look similar to Mediafront's, where 1.9 is the "other"
Comment #4
DanZ commentedI'm not sure that it's possible to have two different 7.x-1.?? releases on the project page at the same time. I.e., if you put the 7.x-1.9-rc1 release up, the 7.x-1.8 release might disappear. I know this did happen on my project when I posted a 7.x-1.0 release. The 7.x-1.0-rc1 release disappeared. I know that it does not happen when you go from a 7.x-1.?? to a 7.x-2.?? release. Note that in the Mediafront example, you've got a 1.5 and 2.0, which are indeed separate.
However, there is a link to the 7.x-1.9-rc1 package on the project page now. It's just not in the usual place. This may be the best possible solution at this time.
Comment #5
rooby commentedThere is now a recommended 1.9 release :)