Child pages
  • Not setting unstable releases as primary download
Skip to end of metadata
Go to start of metadata

Imported From:

Right now, when new In-Portal or it's module version comes out we set it as primary. This results as default download when users clicks to download In-Portal or it's module.

Monitoring downloads from page and comparing them to new topics created at forums I realized that most of people, who download In-Portal don't understand the difference between

  • beta (B)
  • release candidate (RC)
  • final

releases. That's why I'm proposing to set only final release as primary on download page.


  1. Yes, I believe Alex has a valid point.

    This is especially problematic when we have new Major Beta releases like

    Let's make Stable downloads as default ones. Alex, would you please arrange