Mailing-List: contact general-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Logging General" <general@logging.apache.org>
Received-SPF: pass (athena.apache.org: domain of grobmeier@gmail.com
 designates 209.85.216.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <87r4zvj9k0.fsf@v35516.1blu.de>
References: 
 <CAPFNcki==7fD3Okc4R4Mv6b9xZLso=DDHxScG-6mxSWdy7mxCg@mail.gmail.com>
 <87ty4sfqqw.fsf@v35516.1blu.de>
 <CAPFNcki1KQm0Wce3PCCj2oEutgVJOEV2srpFknNRcRaOrz1U3w@mail.gmail.com>
 <87r4zvj9k0.fsf@v35516.1blu.de>
From: Christian Grobmeier <grobmeier@gmail.com>
Date: Fri, 23 Dec 2011 22:04:23 +0100
Message-ID: 
 <CAPFNckjup1JMJyHNeahYtdkq+iqFAnii0XeWNvih7kCxVnU9_g@mail.gmail.com>
Subject: Re: Moving from svn up to mvn site-deploy
To: Logging General <general@logging.apache.org>
Cc: Ivan Habunek <ivan.habunek@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Dec 23, 2011 at 9:51 PM, Stefan Bodewig <bodewig@apache.org> wrote:
> On 2011-12-23, Christian Grobmeier wrote:
>
>> On Thu, Dec 22, 2011 at 6:41 PM, Stefan Bodewig <bodewig@apache.org> wro=
te:
>>> On 2011-12-21, Christian Grobmeier wrote:
>
>>> svnpubsub would solve that and even make the infra crew happy or at
>>> least happier than with a "files on people.apache.org" solution.
>
>> hm besides the code: http://bit.ly/uJs5mQ
>> I could not find any docs. But I heard of it... is it still preferred,
>> because of the ASF CMS?
>
> While looking for information I can link to I stumbled over
> <http://www.apache.org/dev/project-site.html#svnpubsub>
>
> This kind of voids your idea of using site-deploy. =C2=A0Or you'd have to
> deploy to a local directory that is a svn copy and commit that (kind of
> what you do now but without updating people.apache.org).

Not only mine. Even for Commons.
I will ask infra if there are additional docs and if this is still true.
If it is true, we need to consider this for whole logging.

Thanks for digging it out and the explaination below.

Have a nice x-mas!
Cheers
Christian

> Ant uses svnpubsub. =C2=A0Just think of it as automating the manual updat=
e
> we've been doing so far - and without the delay between commit and
> "visible on the live site". =C2=A0All we'd have to do was opening a JIRA
> ticket with infra and point them to the svn directory to publish.
>
> <http://www.apache.org/dev/cms.html#svnpubsub> doesn't say much more
> than that either (but the page as such explains infra's rationale for
> builing the CMS and how they want to manage sites in the future). =C2=A0O=
ne
> important point against site-deploy and any other technology that
> requires to sync files from people.apache.org is the big amount of data
> to scan and sync as the ASF grows. =C2=A0This isn't related to desaster
> recovery at all.
>
> Stefan


--=20
http://www.grobmeier.de
https://www.timeandbill.de