Joost Andrae wrote:
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
This will be difficult when not using numbers. ;-)
If you still want to differntiate between all codelines and avoid
numbers, then you have to use names that make clear what the direction
is like CURRENT, LATEST, FUTURE, NEXT, DEV, OOODEV, etc.
But how to know that CURRENT is 3.0.x (OOO300) and LATEST is 3.1.x
(DEV300), or was it vice versa? ;-) You see it's difficult to handle.
My intenstion is to have only 1 location for all non-release builds. Now
we can use one of the above names or a diffent one. The name shouldn't
be the main part, but simplifing the location structure.
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.
What is the difference between trunk and branch? If you don't write a
longer description onto the website everybody will misunderstood the names.
IMHO the better way is to have 1 website for all builds that aren't a
final release. On this website we can differenciate to the RCs, Dev
Builds and what ever in sections or columns.
download.openoffice.org/index.html | other.html
|------------
/\ |
/ \ |
trunk branch 2.4.2
I don't care about the 2.4.x codeline. We can build a special website
for this when a next release is build and can forget/delete it when it's
finally out.
For official releases (not release candidates) we should stay as it is
Of course this will be untouched and remains the same.
Best regards
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
