Re: [RELEASE]: proposed directory structure on dist
On Thu, May 3, 2012 at 10:15 PM, Kay Schenk kay.sch...@gmail.com wrote: On 05/02/2012 09:48 PM, Roberto Galoppini wrote: On Thu, May 3, 2012 at 12:55 AM, Kay Schenkkay.sch...@gmail.com wrote: On 05/02/2012 03:04 AM, J�rgen Schmidt wrote: Hi, to sum up this longer thread and the structure how I will upload the bits Source release reflecting a future directory structure already: .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.bz2 .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.gz .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.zip .../incubator/ooo/3.4.0/source/... Binary releases keeping the old structure: .../incubator/ooo/files/stable/3.4.0/... .../incubator/ooo/files/localized/ar/3.4.0/... .../incubator/ooo/files/localized/cs/3.4.0/... .../incubator/ooo/files/localized/de/3.4.0/... .../incubator/ooo/files/localized/en-BG/3.4.0/... .../incubator/ooo/files/localized/es/3.4.0/... .../incubator/ooo/files/localized/fr/3.4.0/... .../incubator/ooo/files/localized/gl/3.4.0/... .../incubator/ooo/files/localized/hu/3.4.0/... .../incubator/ooo/files/localized/it/3.4.0/... .../incubator/ooo/files/localized/ja/3.4.0/... .../incubator/ooo/files/localized/nl/3.4.0/... .../incubator/ooo/files/localized/pt-BR/3.4.0/... .../incubator/ooo/files/localized/ru/3.4.0/... .../incubator/ooo/files/localized/zh-CN/3.4.0/... .../incubator/ooo/files/localized/zh-TW/3.4.0/... The directories will include all files (including the checksum files) for all platforms and the language packs. The SDK is available in en-US only and o only in ...files/stable Juergen Thanks again for keeping things as they were for the time being. Hi all, We've loaded the current files, please let us know when youupload more files, so that we can update the rest in a timely manner. Roberto-- Hi. Well my test index page worked well with my linux setup for client download -- i.e. from files/stable/3.4.0/Apache_OpenOffice_incubating_3.4.0_Linux_x86_install-rpm_en-US.tar.gz/download so happy so far. :) Thanks for the feedback. Roberto Please note that the 3.4.0 folder is staged on sourceforge, which means that directly links to files in it will work, but visitors browsing the files will not see them. By the way, is someone coordinating with MirrorBrain maintainers to manage updates to serve the Look for updates function? Roberto -- MzK Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out. -- Ironic, Alanis Morissette -- MzK Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out. -- Ironic, Alanis Morissette -- This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
Re: [RELEASE]: proposed directory structure on dist
On 5/2/12 12:23 AM, Marcus (OOo) wrote: Am 05/01/2012 11:09 PM, schrieb Juergen Schmidt: On Tuesday, 1. May 2012 at 22:11, Marcus (OOo) wrote: Am 05/01/2012 08:23 PM, schrieb Jürgen Schmidt: On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. Maybe it will look more clean but thats not important. Normally the average user should not be pointed to a mirror to find her/his favorite file. For this we have the user-friendly and one-click-download webpages. For the former OOo release the structure was very good and also scalable for new releases and languages. And it is much easier to upload everything into a flat structure. I can't really see a flat structure in the old directory tree. One directory for each language etc. OK, maybe it was not the right wording and my thinking not correct. So, your idea is the following: root path/ooo/version/source/... root path/ooo/version/platform/... root path/ooo/version/platform/languagepacks/... It seems there is not other ASF project with releases for specific platforms *and* languages (otherwise please point me to the project), so maybe we can stick with this and divide only into platform-specifc directories. Maybe we can agree on the following structure for a AOO 3.5 release? root path/dist/incubator/ooo/version/src/... root path/dist/incubator/ooo/version/bin/platform/... why should we add a further indirection bin here? Keep it simple! Either we split in different platform directories or we can use one for all but not both. We will discuss the future structure in new thread asap to have enough time to adapt the scripts. Juergen If necessary we can provide additional files as subdirs inside the version/ directory (e.g., documentation in docs/, hotfixes in patches/, etc.). And new releases as Beta or RC can be uploaded into a new and own version/ subdirectory. BTW: The checksum files are created for every file and checksum format separately, right? Do we have to store them together with the respective files? Or is it allowed to store them in a separate directory? To have every version, platform and language in its own directory is much more complicated to handle in the DL scripts. My proposed structure used the version as start directory and than only split the platforms and the language packs but that can be dropped if it makes things easier. Then we would have a very flat structure. I would prefer to have them together with the full builds. I really don't see here a technical problem to put the already collected items (platform, lang, version, mirror...) in the right order to prepare a download url. There is indeed no technical problem. It's
Re: [RELEASE]: proposed directory structure on dist
Juergen, So I assume we will have 16 language packages? I need double check them then. Best regards, Lily 2012/4/27 Jürgen Schmidt jogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen
Re: [RELEASE]: proposed directory structure on dist
On 5/2/12 11:07 AM, Xia Zhao wrote: Juergen, So I assume we will have 16 language packages? I need double check them then. exactly 16 language packs Juergen Best regards, Lily 2012/4/27 Jürgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen
Re: [RELEASE]: proposed directory structure on dist
Hi, to sum up this longer thread and the structure how I will upload the bits Source release reflecting a future directory structure already: .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.bz2 .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.gz .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.zip .../incubator/ooo/3.4.0/source/... Binary releases keeping the old structure: .../incubator/ooo/files/stable/3.4.0/... .../incubator/ooo/files/localized/ar/3.4.0/... .../incubator/ooo/files/localized/cs/3.4.0/... .../incubator/ooo/files/localized/de/3.4.0/... .../incubator/ooo/files/localized/en-BG/3.4.0/... .../incubator/ooo/files/localized/es/3.4.0/... .../incubator/ooo/files/localized/fr/3.4.0/... .../incubator/ooo/files/localized/gl/3.4.0/... .../incubator/ooo/files/localized/hu/3.4.0/... .../incubator/ooo/files/localized/it/3.4.0/... .../incubator/ooo/files/localized/ja/3.4.0/... .../incubator/ooo/files/localized/nl/3.4.0/... .../incubator/ooo/files/localized/pt-BR/3.4.0/... .../incubator/ooo/files/localized/ru/3.4.0/... .../incubator/ooo/files/localized/zh-CN/3.4.0/... .../incubator/ooo/files/localized/zh-TW/3.4.0/... The directories will include all files (including the checksum files) for all platforms and the language packs. The SDK is available in en-US only and o only in ...files/stable Juergen
Re: [RELEASE]: proposed directory structure on dist
On May 2, 2012, at 3:04 AM, Jürgen Schmidt wrote: Hi, to sum up this longer thread and the structure how I will upload the bits Source release reflecting a future directory structure already: .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.bz2 .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.gz .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.zip .../incubator/ooo/3.4.0/source/... Binary releases keeping the old structure: .../incubator/ooo/files/stable/3.4.0/... .../incubator/ooo/files/localized/ar/3.4.0/... .../incubator/ooo/files/localized/cs/3.4.0/... .../incubator/ooo/files/localized/de/3.4.0/... .../incubator/ooo/files/localized/en-BG/3.4.0/... Do you mean en-GB? .../incubator/ooo/files/localized/es/3.4.0/... .../incubator/ooo/files/localized/fr/3.4.0/... .../incubator/ooo/files/localized/gl/3.4.0/... .../incubator/ooo/files/localized/hu/3.4.0/... .../incubator/ooo/files/localized/it/3.4.0/... .../incubator/ooo/files/localized/ja/3.4.0/... .../incubator/ooo/files/localized/nl/3.4.0/... .../incubator/ooo/files/localized/pt-BR/3.4.0/... .../incubator/ooo/files/localized/ru/3.4.0/... .../incubator/ooo/files/localized/zh-CN/3.4.0/... .../incubator/ooo/files/localized/zh-TW/3.4.0/... The directories will include all files (including the checksum files) for all platforms and the language packs. The SDK is available in en-US only and o only in ...files/stable Thanks for all of your hard work as Release Manager! Regards, Dave Juergen
Re: [RELEASE]: proposed directory structure on dist
On Wednesday, 2. May 2012 at 17:02, Dave Fisher wrote: On May 2, 2012, at 3:04 AM, Jürgen Schmidt wrote: Hi, to sum up this longer thread and the structure how I will upload the bits Source release reflecting a future directory structure already: .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.bz2 .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.gz .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.zip .../incubator/ooo/3.4.0/source/... Binary releases keeping the old structure: .../incubator/ooo/files/stable/3.4.0/... .../incubator/ooo/files/localized/ar/3.4.0/... .../incubator/ooo/files/localized/cs/3.4.0/... .../incubator/ooo/files/localized/de/3.4.0/... .../incubator/ooo/files/localized/en-BG/3.4.0/... Do you mean en-GB? Yes, I hope I have no real typo. Have to check it when I am at home. In the subway right now... Juergen .../incubator/ooo/files/localized/es/3.4.0/... .../incubator/ooo/files/localized/fr/3.4.0/... .../incubator/ooo/files/localized/gl/3.4.0/... .../incubator/ooo/files/localized/hu/3.4.0/... .../incubator/ooo/files/localized/it/3.4.0/... .../incubator/ooo/files/localized/ja/3.4.0/... .../incubator/ooo/files/localized/nl/3.4.0/... .../incubator/ooo/files/localized/pt-BR/3.4.0/... .../incubator/ooo/files/localized/ru/3.4.0/... .../incubator/ooo/files/localized/zh-CN/3.4.0/... .../incubator/ooo/files/localized/zh-TW/3.4.0/... The directories will include all files (including the checksum files) for all platforms and the language packs. The SDK is available in en-US only and o only in ...files/stable Thanks for all of your hard work as Release Manager! Regards, Dave Juergen
Re: [RELEASE]: proposed directory structure on dist
Am 05/02/2012 08:54 AM, schrieb Jürgen Schmidt: On 5/2/12 12:23 AM, Marcus (OOo) wrote: Am 05/01/2012 11:09 PM, schrieb Juergen Schmidt: On Tuesday, 1. May 2012 at 22:11, Marcus (OOo) wrote: Am 05/01/2012 08:23 PM, schrieb Jürgen Schmidt: On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. Maybe it will look more clean but thats not important. Normally the average user should not be pointed to a mirror to find her/his favorite file. For this we have the user-friendly and one-click-download webpages. For the former OOo release the structure was very good and also scalable for new releases and languages. And it is much easier to upload everything into a flat structure. I can't really see a flat structure in the old directory tree. One directory for each language etc. OK, maybe it was not the right wording and my thinking not correct. So, your idea is the following: root path/ooo/version/source/... root path/ooo/version/platform/... root path/ooo/version/platform/languagepacks/... It seems there is not other ASF project with releases for specific platforms *and* languages (otherwise please point me to the project), so maybe we can stick with this and divide only into platform-specifc directories. Maybe we can agree on the following structure for a AOO 3.5 release? root path/dist/incubator/ooo/version/src/... root path/dist/incubator/ooo/version/bin/platform/... why should we add a further indirection bin here? Keep it simple! Either we split in different platform directories or we can use one for all but not both. Because with your initial path structure proposal I thought you want to be more Apache-compliance. Other projects have this setup. Of course we don't need to copy this. :-) We will discuss the future structure in new thread asap to have enough time to adapt the scripts. OK Marcus If necessary we can provide additional files as subdirs inside the version/ directory (e.g., documentation in docs/, hotfixes in patches/, etc.). And new releases as Beta or RC can be uploaded into a new and own version/ subdirectory. BTW: The checksum files are created for every file and checksum format separately, right? Do we have to store them together with the respective files? Or is it allowed to store them in a separate directory? To have every version, platform and language in its own directory is much more complicated to handle in the DL scripts. My proposed structure used the version as start directory and than only split the platforms and the language packs but that can be dropped if it makes things easier. Then we would have a very flat structure. I would prefer to have them together with
Re: [RELEASE]: proposed directory structure on dist
Am 05/02/2012 06:00 PM, schrieb Juergen Schmidt: On Wednesday, 2. May 2012 at 17:02, Dave Fisher wrote: On May 2, 2012, at 3:04 AM, Jürgen Schmidt wrote: Hi, to sum up this longer thread and the structure how I will upload the bits Source release reflecting a future directory structure already: .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.bz2 .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.gz .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.zip .../incubator/ooo/3.4.0/source/... Binary releases keeping the old structure: .../incubator/ooo/files/stable/3.4.0/... .../incubator/ooo/files/localized/ar/3.4.0/... .../incubator/ooo/files/localized/cs/3.4.0/... .../incubator/ooo/files/localized/de/3.4.0/... .../incubator/ooo/files/localized/en-BG/3.4.0/... Do you mean en-GB? Yes, I hope I have no real typo. Have to check it when I am at home. In the subway right now... Juergen .../incubator/ooo/files/localized/es/3.4.0/... .../incubator/ooo/files/localized/fr/3.4.0/... .../incubator/ooo/files/localized/gl/3.4.0/... .../incubator/ooo/files/localized/hu/3.4.0/... .../incubator/ooo/files/localized/it/3.4.0/... .../incubator/ooo/files/localized/ja/3.4.0/... .../incubator/ooo/files/localized/nl/3.4.0/... .../incubator/ooo/files/localized/pt-BR/3.4.0/... .../incubator/ooo/files/localized/ru/3.4.0/... .../incubator/ooo/files/localized/zh-CN/3.4.0/... .../incubator/ooo/files/localized/zh-TW/3.4.0/... The directories will include all files (including the checksum files) for all platforms and the language packs. The SDK is available in en-US only and o only in ...files/stable Looks good from my point of view. Thanks for all of your hard work as Release Manager! Yes, also my side big thanks for your work. Marcus
Re: [RELEASE]: proposed directory structure on dist
On 05/02/2012 03:04 AM, Jürgen Schmidt wrote: Hi, to sum up this longer thread and the structure how I will upload the bits Source release reflecting a future directory structure already: .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.bz2 .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.gz .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.zip .../incubator/ooo/3.4.0/source/... Binary releases keeping the old structure: .../incubator/ooo/files/stable/3.4.0/... .../incubator/ooo/files/localized/ar/3.4.0/... .../incubator/ooo/files/localized/cs/3.4.0/... .../incubator/ooo/files/localized/de/3.4.0/... .../incubator/ooo/files/localized/en-BG/3.4.0/... .../incubator/ooo/files/localized/es/3.4.0/... .../incubator/ooo/files/localized/fr/3.4.0/... .../incubator/ooo/files/localized/gl/3.4.0/... .../incubator/ooo/files/localized/hu/3.4.0/... .../incubator/ooo/files/localized/it/3.4.0/... .../incubator/ooo/files/localized/ja/3.4.0/... .../incubator/ooo/files/localized/nl/3.4.0/... .../incubator/ooo/files/localized/pt-BR/3.4.0/... .../incubator/ooo/files/localized/ru/3.4.0/... .../incubator/ooo/files/localized/zh-CN/3.4.0/... .../incubator/ooo/files/localized/zh-TW/3.4.0/... The directories will include all files (including the checksum files) for all platforms and the language packs. The SDK is available in en-US only and o only in ...files/stable Juergen Thanks again for keeping things as they were for the time being. -- MzK Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out. -- Ironic, Alanis Morissette
Re: [RELEASE]: proposed directory structure on dist
On Thu, May 3, 2012 at 12:55 AM, Kay Schenk kay.sch...@gmail.com wrote: On 05/02/2012 03:04 AM, Jürgen Schmidt wrote: Hi, to sum up this longer thread and the structure how I will upload the bits Source release reflecting a future directory structure already: .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.bz2 .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.tar.gz .../incubator/ooo/3.4.0/source/aoo-3.4.0-incubating-src.zip .../incubator/ooo/3.4.0/source/... Binary releases keeping the old structure: .../incubator/ooo/files/stable/3.4.0/... .../incubator/ooo/files/localized/ar/3.4.0/... .../incubator/ooo/files/localized/cs/3.4.0/... .../incubator/ooo/files/localized/de/3.4.0/... .../incubator/ooo/files/localized/en-BG/3.4.0/... .../incubator/ooo/files/localized/es/3.4.0/... .../incubator/ooo/files/localized/fr/3.4.0/... .../incubator/ooo/files/localized/gl/3.4.0/... .../incubator/ooo/files/localized/hu/3.4.0/... .../incubator/ooo/files/localized/it/3.4.0/... .../incubator/ooo/files/localized/ja/3.4.0/... .../incubator/ooo/files/localized/nl/3.4.0/... .../incubator/ooo/files/localized/pt-BR/3.4.0/... .../incubator/ooo/files/localized/ru/3.4.0/... .../incubator/ooo/files/localized/zh-CN/3.4.0/... .../incubator/ooo/files/localized/zh-TW/3.4.0/... The directories will include all files (including the checksum files) for all platforms and the language packs. The SDK is available in en-US only and o only in ...files/stable Juergen Thanks again for keeping things as they were for the time being. Hi all, We've loaded the current files, please let us know when youupload more files, so that we can update the rest in a timely manner. Please note that the 3.4.0 folder is staged on sourceforge, which means that directly links to files in it will work, but visitors browsing the files will not see them. By the way, is someone coordinating with MirrorBrain maintainers to manage updates to serve the Look for updates function? Roberto -- MzK Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out. -- Ironic, Alanis Morissette -- This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
Re: [RELEASE]: proposed directory structure on dist
On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. And it will work for future releases as well. I have agreed to use the same structure as for 3.3 but I also have said that I skip the version in the localized folder because we already have it in the path. No direct feedback on this and I took it as common consensus. But now I am confused. We should clarify the structure before I will start the upload tomorrow. I haven't looked in the details behind the download scripts and don't know how much work it is to adapt them to a new directory structure. That means I will use the structure that will work for now. Juergen I CAN change the friendly scripts to go with the NEW (Apache) structure. In fact I'm going to work on THAT approach today (along with Rob's changes) and hopefully we'll be set for either instance. To setup a new structure that makes maybe more sense can be done later for a release after 3.4.x. my 2 ct Marcus This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
Re: [RELEASE]: proposed directory structure on dist
On Tue, May 1, 2012 at 11:23 AM, Jürgen Schmidt jogischm...@googlemail.comwrote: On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/**language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. Your very first suggestion would entail *really* major changes right now, so this is the LEAST of my favorite! That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. And it will work for future releases as well. I have agreed to use the same structure as for 3.3 but I also have said that I skip the version in the localized folder because we already have it in the path. No direct feedback on this and I took it as common consensus. OK, I don't understand this last bit. Please again take a look at to the current setup on SourceForge: DL url/files/localized/language-code/3.4.0/packages It would simplify our rollout if we could just stick with the current structure on SourceForge. We will be using that as our primary DL mirror for clients. Marcus's alternate suggestion of : root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... seems like a good option to me as well, and you responded to this. But, the least amount of change -- i.e. keeping the structure we have -- is really the best at this point in terms of getting something done in a reasonable time. Maybe we could discuss alternatives for *after* 3.4 in the future? We are planning on a retool of the DL script after this, and incorporating easier ways to deal with changes like this are high on the priority list. Right now, we are planning on using SF for the majority of downloads -- typical clients -- and that structure -- good or bad -- is already in place, and the test DL script is working based on this. We will probably only use the Apache dist system for source. So, in terms of how you setup things there I don't really care, but, of course, we need information about that. As silly as this probably seems to you, could we PLEASE just stick with the current structure for now? But now I am confused. We should clarify the structure before I will start the upload tomorrow. I haven't looked in the details behind the download scripts and don't know how much work it is to adapt them to a new directory structure. That means I will use the structure that will work for now. Juergen I CAN change the friendly scripts to go with the NEW (Apache) structure. In fact I'm going to work on THAT approach today (along with Rob's changes) and hopefully we'll be set for either instance. To setup a new structure that makes maybe more sense can be done later for a release after 3.4.x. my 2 ct Marcus This e- mail message is intended only for the named recipient(s) above. It may contain
Re: [RELEASE]: proposed directory structure on dist
Am 05/01/2012 08:23 PM, schrieb Jürgen Schmidt: On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. Maybe it will look more clean but thats not important. Normally the average user should not be pointed to a mirror to find her/his favorite file. For this we have the user-friendly and one-click-download webpages. For the former OOo release the structure was very good and also scalable for new releases and languages. And it is much easier to upload everything into a flat structure. To have every version, platform and language in its own directory is much more complicated to handle in the DL scripts. Currently we can assume that all platform files are in the same location. You would like to split them up into different this has to be taken into account. Plus the lanuages. And it will work for future releases as well. I have agreed to use the same structure as for 3.3 but I also have said that I skip the version in the localized folder because we already have it in the path. No direct feedback on this and I took it as common consensus. But now I am confused. We should clarify the structure before I will start the upload tomorrow. To make it short (and maybe painful ;-) ). When you don't create the sam edirectory structure than for OOo 3.3.0, then I'm pretty sure the DL logic will not work. For the structure as reference please have a look here: http://openoffice.mirrorbrain.org/files/stable/3.3.0/ http://openoffice.mirrorbrain.org/files/localized/de/3.3.0/ So, when you will start the upload tomorrow, I think we are pretty close to our official release. IMHO too less time to rework the DL logic for a new structure. I haven't looked in the details behind the download scripts and don't know how much work it is to adapt them to a new directory structure. That means I will use the structure that will work for now. Thanks. I really believe you that you want to improve the structure (e.g., I could think of the split into stable and localized, this is IMHO no longer needed and could be brought together) but we shouldn't change this now. Marcus I CAN change the friendly scripts to go with the NEW (Apache) structure. In fact I'm going to work on THAT approach today (along with Rob's changes) and hopefully we'll be set for either instance. To setup a new structure that makes maybe more sense can be done later for a release after 3.4.x. my 2 ct Marcus This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of
Re: [RELEASE]: proposed directory structure on dist
On Tue, May 1, 2012 at 4:11 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 05/01/2012 08:23 PM, schrieb Jürgen Schmidt: On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. Maybe it will look more clean but thats not important. Normally the average user should not be pointed to a mirror to find her/his favorite file. For this we have the user-friendly and one-click-download webpages. For the former OOo release the structure was very good and also scalable for new releases and languages. And it is much easier to upload everything into a flat structure. To have every version, platform and language in its own directory is much more complicated to handle in the DL scripts. One difference between how did it before now: On the Apache mirrors will only keep the most recent release. We don't keep the complete history of previous releases, not even the history of Apache releases. (Those go to archive.apache.org). So when we do a new release, we need to remove the old one from the Apache servers. So have versions as directory roots, instead of languages as roots, makes this a lot easier. Of course a script can do anything. Currently we can assume that all platform files are in the same location. You would like to split them up into different this has to be taken into account. Plus the lanuages. And it will work for future releases as well. I have agreed to use the same structure as for 3.3 but I also have said that I skip the version in the localized folder because we already have it in the path. No direct feedback on this and I took it as common consensus. But now I am confused. We should clarify the structure before I will start the upload tomorrow. To make it short (and maybe painful ;-) ). When you don't create the sam edirectory structure than for OOo 3.3.0, then I'm pretty sure the DL logic will not work. For the structure as reference please have a look here: http://openoffice.mirrorbrain.org/files/stable/3.3.0/ http://openoffice.mirrorbrain.org/files/localized/de/3.3.0/ So, when you will start the upload tomorrow, I think we are pretty close to our official release. IMHO too less time to rework the DL logic for a new structure. I haven't looked in the details behind the download scripts and don't know how much work it is to adapt them to a new directory structure. That means I will use the structure that will work for now. Thanks. I really believe you that you want to improve the structure (e.g., I could think of the split into stable and localized, this is IMHO no longer needed and could be brought together) but we
Re: [RELEASE]: proposed directory structure on dist
On Tuesday, 1. May 2012 at 22:10, Kay Schenk wrote: On Tue, May 1, 2012 at 11:23 AM, Jürgen Schmidt jogischm...@googlemail.comwrote: On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/**language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. Your very first suggestion would entail *really* major changes right now, so this is the LEAST of my favorite! That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. And it will work for future releases as well. I have agreed to use the same structure as for 3.3 but I also have said that I skip the version in the localized folder because we already have it in the path. No direct feedback on this and I took it as common consensus. OK, I don't understand this last bit. Well I gave a very clear example how I planned to organize the bits on dist based on a structure that came from Marcus . And this was slightly different than the former structure but closer to my proposal. And no clear veto or response so I took it as accepted. Please again take a look at to the current setup on SourceForge: DL url/files/localized/language-code/3.4.0/packages It would simplify our rollout if we could just stick with the current structure on SourceForge. We will be using that as our primary DL mirror for clients. We will do that but in general the dist folder should be our reference for all mirrors. Marcus's alternate suggestion of : root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... seems like a good option to me as well, and you responded to this. But, the least amount of change -- i.e. keeping the structure we have -- is really the best at this point in terms of getting something done in a reasonable time. Maybe we could discuss alternatives for *after* 3.4 in the future? We are planning on a retool of the DL script after this, and incorporating easier ways to deal with changes like this are high on the priority list. Right now, we are planning on using SF for the majority of downloads -- typical clients -- and that structure -- good or bad -- is already in place, and the test DL script is working based on this. taken and we will keep the old structure We will probably only use the Apache
Re: [RELEASE]: proposed directory structure on dist
On Tuesday, 1. May 2012 at 22:11, Marcus (OOo) wrote: Am 05/01/2012 08:23 PM, schrieb Jürgen Schmidt: On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. Maybe it will look more clean but thats not important. Normally the average user should not be pointed to a mirror to find her/his favorite file. For this we have the user-friendly and one-click-download webpages. For the former OOo release the structure was very good and also scalable for new releases and languages. And it is much easier to upload everything into a flat structure. I can't really see a flat structure in the old directory tree. One directory for each language etc. To have every version, platform and language in its own directory is much more complicated to handle in the DL scripts. My proposed structure used the version as start directory and than only split the platforms and the language packs but that can be dropped if it makes things easier. Then we would have a very flat structure. I really don't see here a technical problem to put the already collected items (platform, lang, version, mirror...) in the right order to prepare a download url. But anyway we will keep the old structure for now Juergen Currently we can assume that all platform files are in the same location. You would like to split them up into different this has to be taken into account. Plus the lanuages. All languages in the same directory only language packs goes in a sub directory. And it will work for future releases as well. I have agreed to use the same structure as for 3.3 but I also have said that I skip the version in the localized folder because we already have it in the path. No direct feedback on this and I took it as common consensus. But now I am confused. We should clarify the structure before I will start the upload tomorrow. To make it short (and maybe painful ;-) ). When you don't create the sam edirectory structure than for OOo 3.3.0, then I'm pretty sure the DL logic will not work. For the structure as reference please have a look here:
Re: [RELEASE]: proposed directory structure on dist
Am 05/01/2012 10:27 PM, schrieb Rob Weir: On Tue, May 1, 2012 at 4:11 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 05/01/2012 08:23 PM, schrieb Jürgen Schmidt: On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. Maybe it will look more clean but thats not important. Normally the average user should not be pointed to a mirror to find her/his favorite file. For this we have the user-friendly and one-click-download webpages. For the former OOo release the structure was very good and also scalable for new releases and languages. And it is much easier to upload everything into a flat structure. To have every version, platform and language in its own directory is much more complicated to handle in the DL scripts. One difference between how did it before now: On the Apache mirrors will only keep the most recent release. We don't keep the complete history of previous releases, not even the history of Apache releases. That's how it worked (more or less) also in the old OOo project. There we had for every language and platform the most recent version and the older were moved to the archive. (Those go to archive.apache.org). So when we do a new release, we need to remove the old one from the Apache servers. So have versions Thats fine. as directory roots, instead of languages as roots, makes this a lot easier. Also this is fine. We can take this into account when we rework the DL logic to support a different directory structure. Of course a script can do anything. Of course, so please, no killer argumentS. ;-) Marcus Currently we can assume that all platform files are in the same location. You would like to split them up into different this has to be taken into account. Plus the lanuages. And it will work for future releases as well. I have agreed to use the same structure as for 3.3 but I also have said that I skip the version in the localized folder because we already have it in the path. No direct feedback on this and I took it as common consensus. But now I am confused. We should clarify the structure before I will start the upload tomorrow. To make it short (and maybe painful ;-) ). When you don't create the sam edirectory structure than for OOo 3.3.0, then I'm pretty sure the DL logic will not work. For the structure as reference please have a look here: http://openoffice.mirrorbrain.org/files/stable/3.3.0/ http://openoffice.mirrorbrain.org/files/localized/de/3.3.0/ So, when you will start the upload tomorrow, I think we are pretty close to our official release. IMHO too less time to rework the DL logic for a new structure. I haven't looked in the details behind the
Re: [RELEASE]: proposed directory structure on dist
On 05/01/2012 01:58 PM, Juergen Schmidt wrote: On Tuesday, 1. May 2012 at 22:10, Kay Schenk wrote: On Tue, May 1, 2012 at 11:23 AM, Jürgen Schmidt jogischm...@googlemail.comwrote: On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/**language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. Your very first suggestion would entail *really* major changes right now, so this is the LEAST of my favorite! That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. And it will work for future releases as well. I have agreed to use the same structure as for 3.3 but I also have said that I skip the version in the localized folder because we already have it in the path. No direct feedback on this and I took it as common consensus. OK, I don't understand this last bit. Well I gave a very clear example how I planned to organize the bits on dist based on a structure that came from Marcus . And this was slightly different than the former structure but closer to my proposal. And no clear veto or response so I took it as accepted. Please again take a look at to the current setup on SourceForge: DL url/files/localized/language-code/3.4.0/packages It would simplify our rollout if we could just stick with the current structure on SourceForge. We will be using that as our primary DL mirror for clients. We will do that but in general the dist folder should be our reference for all mirrors. hmmm...OK, I see what you're saying...someone is coordinating this with SourceForge I take it? Or...what needs to be done? A thousand THANK YOUs for leaving things as they are! Marcus's alternate suggestion of : root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... seems like a good option to me as well, and you responded to this. But, the least amount of change -- i.e. keeping the structure we have -- is really the best at this point in terms of getting something done in a reasonable time. Maybe we could discuss alternatives for *after* 3.4 in the future? We are planning on a retool of the DL script after this, and incorporating easier ways to deal with changes like this are high on the priority list. Right now, we are planning on using SF for the majority of downloads -- typical clients -- and that structure -- good or bad -- is already in place, and the test DL script is working based on this. taken and we will keep the old structure We will probably only use the Apache dist system for source. So, in terms of how you setup things there I don't really care, but, of course, we need information about that. well we
Re: [RELEASE]: proposed directory structure on dist
Am 05/01/2012 11:09 PM, schrieb Juergen Schmidt: On Tuesday, 1. May 2012 at 22:11, Marcus (OOo) wrote: Am 05/01/2012 08:23 PM, schrieb Jürgen Schmidt: On 4/30/12 11:16 PM, Kay Schenk wrote: On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I am currently also confused. I would still prefer my proposed structure in the beginning of this thread if it is possible. That would allow us to easy add further platforms and keep the bits a little bit separated. Think about 100 languages and 5 files (including the checksum files) for each downloadable file. Maybe it will look more clean but thats not important. Normally the average user should not be pointed to a mirror to find her/his favorite file. For this we have the user-friendly and one-click-download webpages. For the former OOo release the structure was very good and also scalable for new releases and languages. And it is much easier to upload everything into a flat structure. I can't really see a flat structure in the old directory tree. One directory for each language etc. OK, maybe it was not the right wording and my thinking not correct. So, your idea is the following: root path/ooo/version/source/... root path/ooo/version/platform/... root path/ooo/version/platform/languagepacks/... It seems there is not other ASF project with releases for specific platforms *and* languages (otherwise please point me to the project), so maybe we can stick with this and divide only into platform-specifc directories. Maybe we can agree on the following structure for a AOO 3.5 release? root path/dist/incubator/ooo/version/src/... root path/dist/incubator/ooo/version/bin/platform/... If necessary we can provide additional files as subdirs inside the version/ directory (e.g., documentation in docs/, hotfixes in patches/, etc.). And new releases as Beta or RC can be uploaded into a new and own version/ subdirectory. BTW: The checksum files are created for every file and checksum format separately, right? Do we have to store them together with the respective files? Or is it allowed to store them in a separate directory? To have every version, platform and language in its own directory is much more complicated to handle in the DL scripts. My proposed structure used the version as start directory and than only split the platforms and the language packs but that can be dropped if it makes things easier. Then we would have a very flat structure. I would prefer to have them together with the full builds. I really don't see here a technical problem to put the already collected items (platform, lang, version, mirror...) in the right order to prepare a download url. There is indeed no technical problem. It's only a problem to get there in time. ;-) But anyway we will keep the old structure for now Thanks again. :-) Marcus Currently we can assume that all platform files are in the same location. You would like to split them up into different this has to be taken into account. Plus the
Re: [RELEASE]: proposed directory structure on dist
On 4/27/12 10:09 PM, Kay Schenk wrote: On 04/27/2012 12:47 PM, Marcus (OOo) wrote: Am 04/27/2012 09:34 PM, schrieb Dave Fisher: On Apr 27, 2012, at 12:12 PM, Marcus (OOo) wrote: Am 04/27/2012 08:49 PM, schrieb J�rgen Schmidt: On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 J�rgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? It won't work because the DL logic is working the old way, and only this way. ;-) The old structure has everything in a single directory. The only separation is for en-US only (stable) and all other languages (localized). When we change the structure now where the builds are physicaly existing, then we have to adapt the complete logic, too, which is an effort that I cannot predict. So, the best solution is to keep the old separation and think about to change this with a new release. Then I would prefer to have every install file for a specific version in a single directory. This makes it the easiest way to assemble download links: Example: root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... ... We can only keep the most current version in Apache dist. All older versions go to the archive. Oh yes, right, then it's only one directory. Marcus right now -- especially with the desire to continue to serve up friendly dl logic in the new /download/3.3.0 directory, this is really and truly critical. Yes, it's true, given the Apache current release dictum, we will only have one directory setup -- /dist/incubator/ooo/files/3.4.0/stable /dist/incubator/ooo/files/3.4.0/localized ok that means I will upload the files in this way .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.asc .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.md5 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/stable/... .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.asc .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.md5 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/localized/de/... .../dist/incubator/ooo/files/3.4.0/localized/ar/... .../dist/incubator/ooo/files/3.4.0/localized/cs/... .../dist/incubator/ooo/files/3.4.0/localized/en-GB/... .../dist/incubator/ooo/files/3.4.0/localized/es/... .../dist/incubator/ooo/files/3.4.0/localized/fr/... .../dist/incubator/ooo/files/3.4.0/localized/gl/... .../dist/incubator/ooo/files/3.4.0/localized/hu/... .../dist/incubator/ooo/files/3.4.0/localized/it/... .../dist/incubator/ooo/files/3.4.0/localized/ja/... .../dist/incubator/ooo/files/3.4.0/localized/nl/... .../dist/incubator/ooo/files/3.4.0/localized/pt-BR/... .../dist/incubator/ooo/files/3.4.0/localized/ru/... .../dist/incubator/ooo/files/3.4.0/localized/zh-CN/... .../dist/incubator/ooo/files/3.4.0/localized/zh-TW/... Note that I don't
Re: [RELEASE]: proposed directory structure on dist
On 4/30/12 9:12 AM, Jürgen Schmidt wrote: On 4/27/12 10:09 PM, Kay Schenk wrote: On 04/27/2012 12:47 PM, Marcus (OOo) wrote: Am 04/27/2012 09:34 PM, schrieb Dave Fisher: On Apr 27, 2012, at 12:12 PM, Marcus (OOo) wrote: Am 04/27/2012 08:49 PM, schrieb J�rgen Schmidt: On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 J�rgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? It won't work because the DL logic is working the old way, and only this way. ;-) The old structure has everything in a single directory. The only separation is for en-US only (stable) and all other languages (localized). When we change the structure now where the builds are physicaly existing, then we have to adapt the complete logic, too, which is an effort that I cannot predict. So, the best solution is to keep the old separation and think about to change this with a new release. Then I would prefer to have every install file for a specific version in a single directory. This makes it the easiest way to assemble download links: Example: root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... ... We can only keep the most current version in Apache dist. All older versions go to the archive. Oh yes, right, then it's only one directory. Marcus right now -- especially with the desire to continue to serve up friendly dl logic in the new /download/3.3.0 directory, this is really and truly critical. Yes, it's true, given the Apache current release dictum, we will only have one directory setup -- /dist/incubator/ooo/files/3.4.0/stable /dist/incubator/ooo/files/3.4.0/localized ok that means I will upload the files in this way .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.asc .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.md5 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/stable/... .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.asc .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.md5 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/localized/de/... .../dist/incubator/ooo/files/3.4.0/localized/ar/... .../dist/incubator/ooo/files/3.4.0/localized/cs/... .../dist/incubator/ooo/files/3.4.0/localized/en-GB/... .../dist/incubator/ooo/files/3.4.0/localized/es/... .../dist/incubator/ooo/files/3.4.0/localized/fr/... .../dist/incubator/ooo/files/3.4.0/localized/gl/... .../dist/incubator/ooo/files/3.4.0/localized/hu/... .../dist/incubator/ooo/files/3.4.0/localized/it/... .../dist/incubator/ooo/files/3.4.0/localized/ja/... .../dist/incubator/ooo/files/3.4.0/localized/nl/... .../dist/incubator/ooo/files/3.4.0/localized/pt-BR/... .../dist/incubator/ooo/files/3.4.0/localized/ru/... .../dist/incubator/ooo/files/3.4.0/localized/zh-CN/...
Re: [RELEASE]: proposed directory structure on dist
On Mon, Apr 30, 2012 at 9:24 AM, Kay Schenk kay.sch...@gmail.com wrote: On Mon, Apr 30, 2012 at 12:12 AM, Jürgen Schmidt jogischm...@googlemail.com wrote: On 4/27/12 10:09 PM, Kay Schenk wrote: On 04/27/2012 12:47 PM, Marcus (OOo) wrote: Am 04/27/2012 09:34 PM, schrieb Dave Fisher: On Apr 27, 2012, at 12:12 PM, Marcus (OOo) wrote: Am 04/27/2012 08:49 PM, schrieb J�rgen Schmidt: On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 J�rgen Schmidtjogischmidt@**googlemail.comjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/incubator/ooohttps://www.apache.org/dist/**incubator/ooo https://www.**apache.org/dist/incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/... 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/**projects/openofficeorg.mirror/**files/http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? It won't work because the DL logic is working the old way, and only this way. ;-) The old structure has everything in a single directory. The only separation is for en-US only (stable) and all other languages (localized). When we change the structure now where the builds are physicaly existing, then we have to adapt the complete logic, too, which is an effort that I cannot predict. So, the best solution is to keep the old separation and think about to change this with a new release. Then I would prefer to have every install file for a specific version in a single directory. This makes it the easiest way to assemble download links: Example: root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... ... We can only keep the most current version in Apache dist. All older versions go to the archive. Oh yes, right, then it's only one directory. Marcus right now -- especially with the desire to continue to serve up friendly dl logic in the new /download/3.3.0 directory, this is really and truly critical. Yes, it's true, given the Apache current release dictum, we will only have one directory setup -- /dist/incubator/ooo/files/3.4.**0/stable /dist/incubator/ooo/files/3.4.**0/localized ok that means I will upload the files in this way .../dist/incubator/ooo/files/**3.4.0/stable/Apache_** OpenOffice_incubating_3.4.0_**MacOS_x86_install_en-US.dmg .../dist/incubator/ooo/files/**3.4.0/stable/Apache_** OpenOffice_incubating_3.4.0_**MacOS_x86_install_en-US.dmg.**asc .../dist/incubator/ooo/files/**3.4.0/stable/Apache_** OpenOffice_incubating_3.4.0_**MacOS_x86_install_en-US.dmg.**md5 .../dist/incubator/ooo/files/**3.4.0/stable/Apache_** OpenOffice_incubating_3.4.0_**MacOS_x86_install_en-US.dmg.**sha1 .../dist/incubator/ooo/files/**3.4.0/stable/Apache_** OpenOffice_incubating_3.4.0_**MacOS_x86_install_en-US.dmg.**sha512 .../dist/incubator/ooo/files/**3.4.0/stable/... .../dist/incubator/ooo/files/**3.4.0/localized/de/Apache_** OpenOffice_incubating_3.4.0_**MacOS_x86_install_de.dmg .../dist/incubator/ooo/files/**3.4.0/localized/de/Apache_** OpenOffice_incubating_3.4.0_**MacOS_x86_install_de.dmg.asc .../dist/incubator/ooo/files/**3.4.0/localized/de/Apache_** OpenOffice_incubating_3.4.0_**MacOS_x86_install_de.dmg.md5 .../dist/incubator/ooo/files/**3.4.0/localized/de/Apache_** OpenOffice_incubating_3.4.0_**MacOS_x86_install_de.dmg.sha1 .../dist/incubator/ooo/files/**3.4.0/localized/de/Apache_** OpenOffice_incubating_3.4.0_**MacOS_x86_install_de.dmg.**sha512 .../dist/incubator/ooo/files/**3.4.0/localized/de/... .../dist/incubator/ooo/files/**3.4.0/localized/ar/... .../dist/incubator/ooo/files/**3.4.0/localized/cs/... .../dist/incubator/ooo/files/**3.4.0/localized/en-GB/...
Re: [RELEASE]: proposed directory structure on dist
On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenk kay.sch...@gmail.com wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. This is not something where it will be easier to clean up later. Thinking ahead, what do we do when we have a new release, like a 3.4.1? And what can we do now to make that future less painful? -Rob
Re: [RELEASE]: proposed directory structure on dist
On Mon, Apr 30, 2012 at 10:00 AM, Rob Weir robw...@apache.org wrote: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenk kay.sch...@gmail.com wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. This is not something where it will be easier to clean up later. Thinking ahead, what do we do when we have a new release, like a 3.4.1? And what can we do now to make that future less painful? -Rob Well, for me anyway (I can't address the machinations of setting this up for actual upload), right now it's a matter of getting what we need to do to work in the next day, hopefully. I have other commitments later in the week, and well, I would like to get to a conclusion on this. This will also effect the links in the new other.html as well. (I think given all this I need to split other.html from the new download/index.html and let someone else work on other. I'm kind of getting into a time crunch.) This being said, maybe the version-centric approach Jurgen has suggested from his most recent post and Marcus suggested (I think) makes sense... Again, since all the scripting will be directed to SF, I just need to know what we're doing. The change to make this happen is not horrendous, butthings need to be tracked down in several places. -- MzK Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out. -- Ironic, Alanis Morissette
Re: [RELEASE]: proposed directory structure on dist
On Apr 30, 2012, at 6:29 AM, Jürgen Schmidt wrote: On 4/30/12 9:12 AM, Jürgen Schmidt wrote: On 4/27/12 10:09 PM, Kay Schenk wrote: On 04/27/2012 12:47 PM, Marcus (OOo) wrote: Am 04/27/2012 09:34 PM, schrieb Dave Fisher: On Apr 27, 2012, at 12:12 PM, Marcus (OOo) wrote: Am 04/27/2012 08:49 PM, schrieb J�rgen Schmidt: On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 J�rgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? It won't work because the DL logic is working the old way, and only this way. ;-) The old structure has everything in a single directory. The only separation is for en-US only (stable) and all other languages (localized). When we change the structure now where the builds are physicaly existing, then we have to adapt the complete logic, too, which is an effort that I cannot predict. So, the best solution is to keep the old separation and think about to change this with a new release. Then I would prefer to have every install file for a specific version in a single directory. This makes it the easiest way to assemble download links: Example: root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... ... We can only keep the most current version in Apache dist. All older versions go to the archive. Oh yes, right, then it's only one directory. Marcus right now -- especially with the desire to continue to serve up friendly dl logic in the new /download/3.3.0 directory, this is really and truly critical. Yes, it's true, given the Apache current release dictum, we will only have one directory setup -- /dist/incubator/ooo/files/3.4.0/stable /dist/incubator/ooo/files/3.4.0/localized ok that means I will upload the files in this way .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.asc .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.md5 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/stable/... .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.asc .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.md5 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/localized/de/... .../dist/incubator/ooo/files/3.4.0/localized/ar/... .../dist/incubator/ooo/files/3.4.0/localized/cs/... .../dist/incubator/ooo/files/3.4.0/localized/en-GB/... .../dist/incubator/ooo/files/3.4.0/localized/es/... .../dist/incubator/ooo/files/3.4.0/localized/fr/... .../dist/incubator/ooo/files/3.4.0/localized/gl/... .../dist/incubator/ooo/files/3.4.0/localized/hu/... .../dist/incubator/ooo/files/3.4.0/localized/it/... .../dist/incubator/ooo/files/3.4.0/localized/ja/...
Re: [RELEASE]: proposed directory structure on dist
On Mon, Apr 30, 2012 at 1:25 PM, Dave Fisher dave2w...@comcast.net wrote: On Apr 30, 2012, at 6:29 AM, Jürgen Schmidt wrote: On 4/30/12 9:12 AM, Jürgen Schmidt wrote: On 4/27/12 10:09 PM, Kay Schenk wrote: On 04/27/2012 12:47 PM, Marcus (OOo) wrote: Am 04/27/2012 09:34 PM, schrieb Dave Fisher: On Apr 27, 2012, at 12:12 PM, Marcus (OOo) wrote: Am 04/27/2012 08:49 PM, schrieb J�rgen Schmidt: On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 J�rgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? It won't work because the DL logic is working the old way, and only this way. ;-) The old structure has everything in a single directory. The only separation is for en-US only (stable) and all other languages (localized). When we change the structure now where the builds are physicaly existing, then we have to adapt the complete logic, too, which is an effort that I cannot predict. So, the best solution is to keep the old separation and think about to change this with a new release. Then I would prefer to have every install file for a specific version in a single directory. This makes it the easiest way to assemble download links: Example: root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... ... We can only keep the most current version in Apache dist. All older versions go to the archive. Oh yes, right, then it's only one directory. Marcus right now -- especially with the desire to continue to serve up friendly dl logic in the new /download/3.3.0 directory, this is really and truly critical. Yes, it's true, given the Apache current release dictum, we will only have one directory setup -- /dist/incubator/ooo/files/3.4.0/stable /dist/incubator/ooo/files/3.4.0/localized ok that means I will upload the files in this way .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.asc .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.md5 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/stable/... .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.asc .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.md5 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/localized/de/... .../dist/incubator/ooo/files/3.4.0/localized/ar/... .../dist/incubator/ooo/files/3.4.0/localized/cs/... .../dist/incubator/ooo/files/3.4.0/localized/en-GB/... .../dist/incubator/ooo/files/3.4.0/localized/es/... .../dist/incubator/ooo/files/3.4.0/localized/fr/... .../dist/incubator/ooo/files/3.4.0/localized/gl/... .../dist/incubator/ooo/files/3.4.0/localized/hu/... .../dist/incubator/ooo/files/3.4.0/localized/it/... .../dist/incubator/ooo/files/3.4.0/localized/ja/...
Re: [RELEASE]: proposed directory structure on dist
Am 04/30/2012 07:21 PM, schrieb Kay Schenk: On Mon, Apr 30, 2012 at 10:00 AM, Rob Weirrobw...@apache.org wrote: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. This is not something where it will be easier to clean up later. Thinking ahead, what do we do when we have a new release, like a 3.4.1? And what can we do now to make that future less painful? -Rob Well, for me anyway (I can't address the machinations of setting this up for actual upload), right now it's a matter of getting what we need to do to work in the next day, hopefully. I have other commitments later in the week, and well, I would like to get to a conclusion on this. This will also effect the links in the new other.html as well. (I think given all this I need to split other.html from the new download/index.html and let someone else work on other. I'm kind of getting into a time crunch.) I can take this over. Once the download links are working in general, it's just a big work of search replace, and to delete the languages we do not support yet, and the same for the platforms, and ... ;-) Marcus This being said, maybe the version-centric approach Jurgen has suggested from his most recent post and Marcus suggested (I think) makes sense... Again, since all the scripting will be directed to SF, I just need to know what we're doing. The change to make this happen is not horrendous, butthings need to be tracked down in several places.
Re: [RELEASE]: proposed directory structure on dist
On Apr 30, 2012, at 10:44 AM, Rob Weir wrote: On Mon, Apr 30, 2012 at 1:25 PM, Dave Fisher dave2w...@comcast.net wrote: On Apr 30, 2012, at 6:29 AM, Jürgen Schmidt wrote: On 4/30/12 9:12 AM, Jürgen Schmidt wrote: On 4/27/12 10:09 PM, Kay Schenk wrote: On 04/27/2012 12:47 PM, Marcus (OOo) wrote: Am 04/27/2012 09:34 PM, schrieb Dave Fisher: On Apr 27, 2012, at 12:12 PM, Marcus (OOo) wrote: Am 04/27/2012 08:49 PM, schrieb J�rgen Schmidt: On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 J�rgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? It won't work because the DL logic is working the old way, and only this way. ;-) The old structure has everything in a single directory. The only separation is for en-US only (stable) and all other languages (localized). When we change the structure now where the builds are physicaly existing, then we have to adapt the complete logic, too, which is an effort that I cannot predict. So, the best solution is to keep the old separation and think about to change this with a new release. Then I would prefer to have every install file for a specific version in a single directory. This makes it the easiest way to assemble download links: Example: root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... ... We can only keep the most current version in Apache dist. All older versions go to the archive. Oh yes, right, then it's only one directory. Marcus right now -- especially with the desire to continue to serve up friendly dl logic in the new /download/3.3.0 directory, this is really and truly critical. Yes, it's true, given the Apache current release dictum, we will only have one directory setup -- /dist/incubator/ooo/files/3.4.0/stable /dist/incubator/ooo/files/3.4.0/localized ok that means I will upload the files in this way .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.asc .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.md5 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/stable/... .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.asc .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.md5 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/localized/de/... .../dist/incubator/ooo/files/3.4.0/localized/ar/... .../dist/incubator/ooo/files/3.4.0/localized/cs/... .../dist/incubator/ooo/files/3.4.0/localized/en-GB/... .../dist/incubator/ooo/files/3.4.0/localized/es/... .../dist/incubator/ooo/files/3.4.0/localized/fr/... .../dist/incubator/ooo/files/3.4.0/localized/gl/... .../dist/incubator/ooo/files/3.4.0/localized/hu/...
Re: [RELEASE]: proposed directory structure on dist
Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. To setup a new structure that makes maybe more sense can be done later for a release after 3.4.x. my 2 ct Marcus
Re: [RELEASE]: proposed directory structure on dist
On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto To setup a new structure that makes maybe more sense can be done later for a release after 3.4.x. my 2 ct Marcus This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
Re: [RELEASE]: proposed directory structure on dist
On 04/30/2012 11:31 AM, Dave Fisher wrote: On Apr 30, 2012, at 10:44 AM, Rob Weir wrote: On Mon, Apr 30, 2012 at 1:25 PM, Dave Fisher dave2w...@comcast.net wrote: On Apr 30, 2012, at 6:29 AM, Jürgen Schmidt wrote: On 4/30/12 9:12 AM, Jürgen Schmidt wrote: On 4/27/12 10:09 PM, Kay Schenk wrote: On 04/27/2012 12:47 PM, Marcus (OOo) wrote: Am 04/27/2012 09:34 PM, schrieb Dave Fisher: On Apr 27, 2012, at 12:12 PM, Marcus (OOo) wrote: Am 04/27/2012 08:49 PM, schrieb J�rgen Schmidt: On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 J�rgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? It won't work because the DL logic is working the old way, and only this way. ;-) The old structure has everything in a single directory. The only separation is for en-US only (stable) and all other languages (localized). When we change the structure now where the builds are physicaly existing, then we have to adapt the complete logic, too, which is an effort that I cannot predict. So, the best solution is to keep the old separation and think about to change this with a new release. Then I would prefer to have every install file for a specific version in a single directory. This makes it the easiest way to assemble download links: Example: root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... ... We can only keep the most current version in Apache dist. All older versions go to the archive. Oh yes, right, then it's only one directory. Marcus right now -- especially with the desire to continue to serve up friendly dl logic in the new /download/3.3.0 directory, this is really and truly critical. Yes, it's true, given the Apache current release dictum, we will only have one directory setup -- /dist/incubator/ooo/files/3.4.0/stable /dist/incubator/ooo/files/3.4.0/localized ok that means I will upload the files in this way .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.asc .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.md5 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/stable/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/stable/... .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.asc .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.md5 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha1 .../dist/incubator/ooo/files/3.4.0/localized/de/Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_de.dmg.sha512 .../dist/incubator/ooo/files/3.4.0/localized/de/... .../dist/incubator/ooo/files/3.4.0/localized/ar/... .../dist/incubator/ooo/files/3.4.0/localized/cs/... .../dist/incubator/ooo/files/3.4.0/localized/en-GB/... .../dist/incubator/ooo/files/3.4.0/localized/es/... .../dist/incubator/ooo/files/3.4.0/localized/fr/... .../dist/incubator/ooo/files/3.4.0/localized/gl/...
Re: [RELEASE]: proposed directory structure on dist
On 04/30/2012 11:13 AM, Marcus (OOo) wrote: Am 04/30/2012 07:21 PM, schrieb Kay Schenk: On Mon, Apr 30, 2012 at 10:00 AM, Rob Weirrobw...@apache.org wrote: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. This is not something where it will be easier to clean up later. Thinking ahead, what do we do when we have a new release, like a 3.4.1? And what can we do now to make that future less painful? -Rob Well, for me anyway (I can't address the machinations of setting this up for actual upload), right now it's a matter of getting what we need to do to work in the next day, hopefully. I have other commitments later in the week, and well, I would like to get to a conclusion on this. This will also effect the links in the new other.html as well. (I think given all this I need to split other.html from the new download/index.html and let someone else work on other. I'm kind of getting into a time crunch.) I can take this over. Once the download links are working in general, it's just a big work of search replace, and to delete the languages we do not support yet, and the same for the platforms, and ... ;-) Marcus Marcus-- I will go ahead and finish with this piece, so no need. I know it's not all that big a deal...I just a bit too frustrated. But...I am going to separate (the new) other.html from the download/index.html business and maybe you could deal with that. Yeah--there's only a few of us that have messed with this stuff before, so somewhat mind-boggling. This being said, maybe the version-centric approach Jurgen has suggested from his most recent post and Marcus suggested (I think) makes sense... Again, since all the scripting will be directed to SF, I just need to know what we're doing. The change to make this happen is not horrendous, butthings need to be tracked down in several places. -- MzK Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out. -- Ironic, Alanis Morissette
Re: [RELEASE]: proposed directory structure on dist
On 04/30/2012 12:47 PM, Roberto Galoppini wrote: On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 04/30/2012 07:00 PM, schrieb Rob Weir: On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenkkay.sch...@gmail.com �wrote: snip Right now I have the DL friendly script setup to only use SF...which is setup in the old way. I don't think we'll be usign Apache for pre-build client downloads. So, I have a question -- who will be setting up the SF packs and will they just stick with the current structure on that system for DLs -- i.e. root/files/stable/version/ pack name and root/files/localized/language/version/pack name I'm hoping the answer is YES. Whatever we do, let's try to get a directory schem that works now and for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This is not something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. Thinking ahead, what do we do when we have a new release, like a 3.4.1? �And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. It seems the easiest way to go to me too. Roberto OK, I need some clarification here -- again. I am to understand by the above statements by Marcus and Roberto that the directory structure for 3.4 will be the same as it is for 3.3, but we will have a *different* structure on www.apache.org/dist? Also, OK, we just need some awareness. So -- can someone tell me what's what here. I CAN change the friendly scripts to go with the NEW (Apache) structure. In fact I'm going to work on THAT approach today (along with Rob's changes) and hopefully we'll be set for either instance. To setup a new structure that makes maybe more sense can be done later for a release after 3.4.x. my 2 ct Marcus This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you. -- MzK Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out. -- Ironic, Alanis Morissette
Re: [RELEASE]: proposed directory structure on dist
2012/4/27 Jürgen Schmidt jogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ -- MzK Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out. -- Ironic, Alanis Morissette
Re: [RELEASE]: proposed directory structure on dist
On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 Jürgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? Juergen
Re: [RELEASE]: proposed directory structure on dist
Am 04/27/2012 08:49 PM, schrieb Jürgen Schmidt: On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 Jürgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? It won't work because the DL logic is working the old way, and only this way. ;-) The old structure has everything in a single directory. The only separation is for en-US only (stable) and all other languages (localized). When we change the structure now where the builds are physicaly existing, then we have to adapt the complete logic, too, which is an effort that I cannot predict. So, the best solution is to keep the old separation and think about to change this with a new release. Then I would prefer to have every install file for a specific version in a single directory. This makes it the easiest way to assemble download links: Example: root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... ... Marcus
Re: [RELEASE]: proposed directory structure on dist
On Apr 27, 2012, at 12:12 PM, Marcus (OOo) wrote: Am 04/27/2012 08:49 PM, schrieb Jürgen Schmidt: On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 Jürgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? It won't work because the DL logic is working the old way, and only this way. ;-) The old structure has everything in a single directory. The only separation is for en-US only (stable) and all other languages (localized). When we change the structure now where the builds are physicaly existing, then we have to adapt the complete logic, too, which is an effort that I cannot predict. So, the best solution is to keep the old separation and think about to change this with a new release. Then I would prefer to have every install file for a specific version in a single directory. This makes it the easiest way to assemble download links: Example: root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... ... We can only keep the most current version in Apache dist. All older versions go to the archive. Regards, Dave Marcus
Re: [RELEASE]: proposed directory structure on dist
On 04/27/2012 12:47 PM, Marcus (OOo) wrote: Am 04/27/2012 09:34 PM, schrieb Dave Fisher: On Apr 27, 2012, at 12:12 PM, Marcus (OOo) wrote: Am 04/27/2012 08:49 PM, schrieb J�rgen Schmidt: On 4/27/12 5:32 PM, Kay Schenk wrote: 2012/4/27 J�rgen Schmidtjogischm...@googlemail.com Hi, to be prepared for the upcoming release I plan to use the following directory structure on https://www.apache.org/dist/**incubator/ooohttps://www.apache.org/dist/incubator/ooo Existing 3.3 3.3/patches 3.3/patches/cve-2012-0037/... DATE KEYS New added: 3.4.0/source 3.4.0/windows/... 3.4.0/windows/languagepacks/..**. 3.4.0/macos/... 3.4.0/macos/languagepacks/... 3.4.0/linux-x86/... 3.4.0/linux-x86/languagepacks/**... 3.4.0/linux-x86-64/... 3.4.0/linux-x86-64/**languagepacks/... 16 languages: en-US ar cs de en-GB es fr gl hu it ja nl ru pr-BR zh-CN zh-TW Do we need to prepare or adapt the download page? Juergen Juergen-- This will considerably change the current logic being used. Is there some reason you don't want to use the existing setup of: root DL area/files/stable/3.4/... root DL area/files/localized/3.4/... see: http://sourceforge.net/projects/openofficeorg.mirror/files/ I had a look to other projects in the dist folder on Apache and looked what we already have. From my point of view the old structure doesn't really make too much sense. Why should we for example put the localized bit in separate directories when we have the language Id as part of the name? And we have only stable releases in the future. Ok we will have archives of older versions but that's it. Do we have the time to adapt it to the new structure. We should do it ow if possible. What do others think? It won't work because the DL logic is working the old way, and only this way. ;-) The old structure has everything in a single directory. The only separation is for en-US only (stable) and all other languages (localized). When we change the structure now where the builds are physicaly existing, then we have to adapt the complete logic, too, which is an effort that I cannot predict. So, the best solution is to keep the old separation and think about to change this with a new release. Then I would prefer to have every install file for a specific version in a single directory. This makes it the easiest way to assemble download links: Example: root-path/files/3.4.0/... root-path/files/3.4.1/... root-path/files/3.5.0/... ... We can only keep the most current version in Apache dist. All older versions go to the archive. Oh yes, right, then it's only one directory. Marcus right now -- especially with the desire to continue to serve up friendly dl logic in the new /download/3.3.0 directory, this is really and truly critical. Yes, it's true, given the Apache current release dictum, we will only have one directory setup -- /dist/incubator/ooo/files/3.4.0/stable /dist/incubator/ooo/files/3.4.0/localized Seriously, once we get past this release, we could and should discuss this some more, but for now...we don't really have time to re-do the logic for a different directory setup -- MzK Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out. -- Ironic, Alanis Morissette
