Hi,
I have a different proposal:
Due to this I think about a few requirements:
1. Avoid version numbers and strings in links
+1
Example:
bad = http://download.openoffice.org/3.0.1rc1/index.html
Because we have to create new directories and files for new builds.
good = http://download.openoffice.org/next/index.html
We can reuse the existing things again and again.
From my POV such a build should be listed at the location of the
development snapshot builds as it currently is used at
http://download.openoffice.org/680
Unfortunately here we have the same issue:
Currently there are three possible branches (OOH680, OOO300 and DEV300)
that may use this page.
I propose to have
http://download.openoffice.org/trunk/ to be used for DEV300 builds
http://download.openoffice.org/branch/ to be used for developer
snapshots and release candidates of current release branches like OOO300
(which is the branch used to release version 3.0.0 and 3.0.1). It also
could be used for a possible OOH680 release candidate (if there is such
a build). Both should be listed on the main download page.
download.openoffice.org/index.html | other.html
|------------
/\ |
/ \ |
trunk branch 2.4.2
For official releases (not release candidates) we should stay as it is
http://download.openoffice.org/index.html (for the one click download)
http://download.openoffice.org/other.html (for the download page
containing the table of localizations/platforms. But here we have the
same issue...there can be several releases at the same time. In the
moment we create pages like http://download.openoffice.org/2.4.2/ that
can be linked from the main download page. I think it is sufficient to
use it like this.
Kind regards, Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
