Kay Schenk wrote:
Hello Kay,
OK, looking at this a bit more, and our current structure in
download.openoffice.org.
IF we would be consistent with the directory naming and what's reflected
on the bouncer URLS, it seems we should be able to parse out the version
from the URL linked by the user, and automatically generate the VERSION
variable for the given version.
Example, I want 2.4.2, I click on download.openoffice.org/2.4.2, I
should be able to generate VERSION = "2.4.2" for the download process
from this.
Is it worth looking into the programming for this? I will say that this
variable is not used in any DL index pages prior to 2.4.2, as the older
index pages have been blanked.
this would be the opposite what IMHO we want to reach: getting rid of
the dependency of version number in links.
I think the idea with global variables is very helpful for maintainance.
If there would a new 2.4.3, then the only thing someone has to do is to
modify the version number in only 1 location. The same for every other
release like Dev Builds and RCs. We (Joost and me) will take care of
unstable builds and every 3 months someone has to look for the variable
for the next stable release (maybe we, too ;-) ).
BTW:
In the meantime I've announced the new Dev Build available with the
"next" download website on relea...@ooo, qa-...@ooo and GullFOSS. Let's
see what feedback we will get for the website.
Thanks
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
