Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 69415 invoked from network); 13 Dec 2010 16:22:03 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Dec 2010 16:22:03 -0000 Received: (qmail 5053 invoked by uid 500); 13 Dec 2010 16:22:03 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 4693 invoked by uid 500); 13 Dec 2010 16:22:01 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 4683 invoked by uid 99); 13 Dec 2010 16:22:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Dec 2010 16:22:00 +0000 X-ASF-Spam-Status: No, hits=1.0 required=10.0 tests=SPF_HELO_PASS,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of nicolas.lalevee@hibnet.org does not designate 216.86.168.183 as permitted sender) Received: from [216.86.168.183] (HELO mxout-08.mxes.net) (216.86.168.183) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Dec 2010 16:21:51 +0000 Received: from hibpro.anyware (unknown [84.14.163.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 2785B509EB for ; Mon, 13 Dec 2010 11:21:29 -0500 (EST) From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: svnpubsub for the Ant and Ivy sites Date: Mon, 13 Dec 2010 17:21:27 +0100 Message-Id: <4EFCB767-8C31-42D2-9BC2-9A47579423A7@hibnet.org> To: Ant Developers List Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) X-Virus-Checked: Checked by ClamAV on apache.org As you may know, the infra team has developed a CMS [1]. I am not = suggesting to change the way we are editing our doc and use this new = CMS, because actually our workflow to publish content on the web is very = close to the CMS one. In Ant: * we edit some file if xdocs and commit them * we generate the corresponding html in docs and commit them * go on people.apache.org and svn up In Ivy and IvyDE: * we edit some xooki-aware html files and commit them * we generate the html files and commit them * go on people.apache.org and svn up As the infra says [2], having the html files on people.a.o is not very = secure and seems to consume lots of resources. So they are suggesting to = using svnpubsub. I didn't find a proper doc about svnpubsub, but as far as I can tell, as = soon as the web pages are in the asf svn, it publish the docs live as = soon as there is a commit, matters of few seconds (or minutes I don't = remember, at least far less than via the rsync on people). So I suggest that we say to the infra team that our sites are there: * https://svn.apache.org/repos/asf/ant/core/trunk/docs/ * https://svn.apache.org/repos/asf/ant/ivy/site/target/ and in our workflow we skip the last part of going on people.a.o and svn = up. So this will speed up the time to publish our web sites and save some = resources on people.a.o. WDYT ? Nicolas [1] https://blogs.apache.org/infra/entry/the_asf_cms [2] http://www.apache.org/dev/cms.html#minotaur --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org