On 7/11/13 10:56 PM, Marcus (OOo) wrote: > Am 07/11/2013 05:41 PM, schrieb Jürgen Schmidt: >> On 7/11/13 9:32 AM, Jürgen Schmidt wrote: >>> On 7/10/13 10:48 PM, Marcus (OOo) wrote: >>>> Am 07/10/2013 10:09 AM, schrieb Jürgen Schmidt: >>>>> On 7/9/13 10:49 PM, Marcus (OOo) wrote: >>>>>> Am 07/09/2013 10:39 AM, schrieb Jürgen Schmidt: >>>>>>> On 7/8/13 11:01 PM, Marcus (OOo) wrote: >>>>>>>> Am 07/08/2013 10:46 PM, schrieb Marcus (OOo): >>>>>>>>> Am 07/08/2013 03:59 PM, schrieb Rob Weir: >>>>>>>>>> On Mon, Jul 8, 2013 at 4:44 AM, Jürgen >>>>>>>>>> Schmidt<jogischm...@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>>> On 7/3/13 4:19 PM, Rob Weir wrote: >>>>>>>>>>>> At the risk of seeming too "corporate", I've added a >>>>>>>>>>>> "dashboard" >>>>>>>>>>>> page >>>>>>>>>>>> to the wiki to track our summary status: >>>>>>>>>>>> >>>>>>>>>>>> https://cwiki.apache.org/confluence/display/OOOUSERS/4.0+Release+Dashboard >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> I hate status reports as much as anyone, but with so much >>>>>>>>>>>> information >>>>>>>>>>>> passing by on our many mailing lists, we risk losing track >>>>>>>>>>>> of the >>>>>>>>>>>> high-level status. I'm hoping that this dash board page, if we >>>>>>>>>>>> update >>>>>>>>>>>> it, can give us all a good view of how the release is >>>>>>>>>>>> progressing. >>>>>>>>>>>> >>>>>>>>>>>> No need for a lot of detail. This is intended to be high-level, >>>>>>>>>>>> identifying areas that are "on track" versus "at risk". Or >>>>>>>>>>>> green/yellow/red. >>>>>>>>>>>> >>>>>>>>>>>> This will also make it easier for volunteers to see what areas >>>>>>>>>>>> need >>>>>>>>>>>> the most help. We have many volunteers who are able to help in >>>>>>>>>>>> more >>>>>>>>>>>> than one area. Now we can see what areas need help. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> indeed it could help but the page was not easy to find when >>>>>>>>>>> losing >>>>>>>>>>> this >>>>>>>>>>> email out of focus. >>>>>>>>>>> >>>>>>>>>>> And I am wondering why it is not placed under Project >>>>>>>>>>> Planning -> >>>>>>>>>>> Releases -> AOO 4.0 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I just moved it there now. URL is the same: >>>>>>>>>> >>>>>>>>>> https://cwiki.apache.org/confluence/display/OOOUSERS/4.0+Release+Dashboard >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> I just saw an entry for the download scripting, so I've added a >>>>>>>>> comment. >>>>>>> >>>>>>> Marcus I know that you have worked on the new directory structure >>>>>>> and >>>>>>> tested it already. Can you please point me to the related >>>>>>> information >>>>>>> that I can prepare my copy scripts accordingly to have them in >>>>>>> place as >>>>>>> well. >>>>>> >>>>>> the files are generally here: >>>>>> http://www.openoffice.org/download/test/ >>>>>> >>>>>> The JavaScript logic is here: >>>>>> http://www.openoffice.org/download/test/download.js >>>>>> >>>>>> Some variables come from here: >>>>>> http://www.openoffice.org/download/test/globalvars.js >>>>>> >>>>>> Test files (empty !) are on my Apache people account: >>>>>> http://people.apache.org/~marcus/aoo/ >>>>>> >>>>>> If you want to see some values from the JS functions and browser, use >>>>>> the analyze webpage: >>>>>> http://www.openoffice.org/download/test/analyze.html >>>>>> >>>>>> And if you have further questions just tell me. >>>>> >>>>> ok thanks >>>>> >>>>> Please take care of the correct file names of the src packages >>>>> >>>>> apache-openoffice-4.0.0-r1499347-src.tar.gz[.md5|sha256] >>>>> apache-openoffice-4.0.0-r1499347-src.tar.bz2[.md5|sha256] >>>>> apache-openoffice-4.0.0-r1499347-src.zip[.md5|sha256] >>> >>> I forgot -> .asc > > OK > >>>> the format is exactly what I have scripted. Now I just need to wait for >>>> the last and final rev number. >>>> >>>> BTW: >>>> I've corrected the filenames in my Apache people account as it was an >>>> older naming. >>>> >>>>> The revision is the tricky part and we introduced it for our language >>>>> update for 3.4.1 >>>>> >>>>> If that is a problem we have to think about a new name >>>> >>>> No, it's fine. >> >> just to double check ... >> >> I will create the following directory structure on dist. I use >> "openoffice" instead of "aoo" for easier identifying. And no other >> project use "apache" in the name here. > > OK, so the full URLs will look like the following: > > http://www.apache.org/dist/openoffice/4.0.0/... > http://sourceforge.net/projects/openoffice/4.0.0/... > > Or different? >
no I think that is correct >> openoffice/4.0.0 >> openoffice/4.0.0/source >> openoffice/4.0.0/binaries >> openoffice/4.0.0/binaries/SDK >> openoffice/4.0.0/binaries/fi >> openoffice/4.0.0/binaries/pt >> openoffice/4.0.0/binaries/ko >> openoffice/4.0.0/binaries/ru >> openoffice/4.0.0/binaries/de >> openoffice/4.0.0/binaries/ja >> openoffice/4.0.0/binaries/el >> openoffice/4.0.0/binaries/sk >> openoffice/4.0.0/binaries/zh-CN >> openoffice/4.0.0/binaries/gd >> openoffice/4.0.0/binaries/it >> openoffice/4.0.0/binaries/sl >> openoffice/4.0.0/binaries/ta >> openoffice/4.0.0/binaries/es >> openoffice/4.0.0/binaries/hu >> openoffice/4.0.0/binaries/gl >> openoffice/4.0.0/binaries/en-GB >> openoffice/4.0.0/binaries/fr >> openoffice/4.0.0/binaries/pt-BR >> openoffice/4.0.0/binaries/ast >> openoffice/4.0.0/binaries/nl >> openoffice/4.0.0/binaries/cs >> openoffice/4.0.0/binaries/en-US > > Yes, looks good. I am still asking why we need the sub directories under binaries? We have the file unique already and the language code is part of the file name. The SDK name is also unique. And normally our users will download via our download page and don't have to seek on their own. Juergen > > Marcus > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
