Return-Path: 
 <ooo-dev-return-17393-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 655F2C16D
	for <apmail-incubator-ooo-dev-archive@minotaur.apache.org>;
 Mon, 30 Apr 2012 18:14:10 +0000 (UTC)
Received: (qmail 822 invoked by uid 500); 30 Apr 2012 18:14:10 -0000
Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org
Received: (qmail 730 invoked by uid 500); 30 Apr 2012 18:14:10 -0000
Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ooo-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:ooo-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:ooo-dev@incubator.apache.org>
List-Id: <ooo-dev.incubator.apache.org>
Reply-To: ooo-dev@incubator.apache.org
Delivered-To: mailing list ooo-dev@incubator.apache.org
Received: (qmail 722 invoked by uid 99); 30 Apr 2012 18:14:10 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2012 18:14:10 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of marcus.mail@wtnet.de
 designates 213.209.103.7 as permitted sender)
Received: from [213.209.103.7] (HELO smtp2.wtnet.de) (213.209.103.7)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2012 18:14:02 +0000
X-WT-Originating-IP: 84.46.106.163
Received: from f9.linux (pop8-672.catv.wtnet.de [84.46.106.163])
	(authenticated bits=0)
	by smtp2.wtnet.de (8.14.4/8.14.4) with ESMTP id q3UIDhnK022321
	(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO)
	for <ooo-dev@incubator.apache.org>; Mon, 30 Apr 2012 20:13:43 +0200
Message-ID: <4F9ED654.1080007@wtnet.de>
Date: Mon, 30 Apr 2012 20:13:40 +0200
From: "Marcus (OOo)" <marcus.mail@wtnet.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de;
 rv:1.9.2.20) Gecko/20110804 Thunderbird/3.1.12
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: [RELEASE]: proposed directory structure on dist
References: <4F9A860F.1070800@googlemail.com>
	<CAGj32142PsRs-poTSnr8h6A3=3mYDQWehZA-kAkqkyjSBZhP8Q@mail.gmail.com>
	<4F9AEA44.7020706@googlemail.com>	<4F9AEF84.1090203@wtnet.de>
	<B57F0349-7AA2-462D-803E-78611DE38D92@comcast.net>
	<4F9AF7D4.4030708@wtnet.de>	<4F9AFCE7.4040303@gmail.com>
	<4F9E3B4C.9040403@googlemail.com>
	<CAGj3215JT00bMEkHb9wq=BWiDDxQOm0eWWrz3mW8E2A77_ZxBw@mail.gmail.com>
	<CAGj3216DLBgmkBnqUSb5Pr85tDfHJ3mKRx3yyeUT8crQAjv-fg@mail.gmail.com>
	<CAP-ksojzRb-Z0d2AWF4-yL6khm0uq7dj6GcHF8XWe3sBZY1=PQ@mail.gmail.com>
 <CAGj32159c1STYqseQFh703e9qa=6GXvz1xS5Z0w2C2eg-1bLcw@mail.gmail.com>
In-Reply-To: 
 <CAGj32159c1STYqseQFh703e9qa=6GXvz1xS5Z0w2C2eg-1bLcw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Am 04/30/2012 07:21 PM, schrieb Kay Schenk:
> On Mon, Apr 30, 2012 at 10:00 AM, Rob Weir<robweir@apache.org>  wrote:
>
>> On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenk<kay.schenk@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,
> but....things need to be tracked down in several places.