/
Not setting unstable releases as primary download
Not setting unstable releases as primary download
Imported From: http://groups.google.com/group/in-portal-org/browse_thread/thread/34f5c68b8954fcfd#
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 http://www.in-portal.com/download.html 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.