Closed Bug 269010 Opened 20 years ago Closed 20 years ago

Product versions support

Categories

(Webtools :: Bouncer, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: morgamic, Assigned: morgamic)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041102 Firefox/1.0RC1 (Debian package 0.99+1.0RC1-3)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041102 Firefox/1.0RC1 (Debian package 0.99+1.0RC1-3)

The current assumed version of every product is the latest version (whichever
the filepath is set to).  This of course does not scale well in the long-term. 
The databse needs to be modified to handle versions, which is a one-to-many
relationship added between products and versions.

An additional added benefit will be the ability to create granular reports based
on product that can list downloads per-version.  If we can manage to get this
wrapped up before the next major release, we'll have much better real-time
statistical estimates to reference to quell curious minds in the waiting period
for actual mirror data.

Reproducible: Always
Steps to Reproduce:
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Version may be passed as an optional argument.  This makes it possible to have a
form that lets a user choose any product, verison, language and OS combination
(and even mirro if they desire) via a simple form that uses a GET method pointed
at /index.php.

That form, of course, doesn't exist yet.  But that capability is there.

For now, we have the ability to define a specific version and that's great.  The
default will always be the latest version based on the Date field defined in the
version's record that may be defined in /admin/versions.php.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
QA Contact: kveton → bouncer
You need to log in before you can comment on or make changes to this bug.