Hi all,
currently we have the pleasure to manage 2 release more or less in
parallel: 3.0.1 and 3.1. Currently 3.0.1 RC1 is out and the next 3.1 Dev
Build is coming soon.
On "download.openoffice.org" we have a colored box as link for
downloading both, RC and Dev Builds. Of course this cannot work when
handling 2 releases in parallel.
Due to this I think about a few requirements:
1. Avoid version numbers and strings in links
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.
2. Keep it simple in the layout
Example:
good = http://download.openoffice.org/index.html
maybe bad = http://download.openoffice.org/other.html
But maybe here it depends on the people we want to reach. It's not the
normal users but the developers, and these are more experienced and can
handle/understand a complex table structure better.
3. Keep it simple to maintain.
Example:
When we have a new stable release only one version string has to be
adjusted in the "http://download.openoffice.org/index.html";. I could
think about the same for RC and Dev Builds.
Possible solution:
When clicking on the "Get Release candidates and Snapshot builds" link,
a new "index.html" will open with 2 columns that offers a) the current
RC (if still available and needed) and b) the next Dev Build.
I'll plan a first HTML file as draft how I think about a possible
solution and will post a link to the file.
Please tell me about your opinions. Am I the only one who sees this as a
problem? Maybe someone has already a solution and maybe a better one?
Best regards
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
