Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 71481 invoked from network); 4 Sep 2009 14:04:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Sep 2009 14:04:35 -0000 Received: (qmail 45181 invoked by uid 500); 4 Sep 2009 14:04:34 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 45161 invoked by uid 500); 4 Sep 2009 14:04:34 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 45153 invoked by uid 99); 4 Sep 2009 14:04:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Sep 2009 14:04:34 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.98.43] (HELO brmea-mail-2.sun.com) (192.18.98.43) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Sep 2009 14:04:21 +0000 Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n84E40As010541 for ; Fri, 4 Sep 2009 14:04:00 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KPG00H009OC7Q00@mail-amer.sun.com> for derby-dev@db.apache.org; Fri, 04 Sep 2009 08:04:00 -0600 (MDT) Received: from [129.148.71.199] ([unknown] [129.148.71.199]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KPG00BJM9QNTY90@mail-amer.sun.com> for derby-dev@db.apache.org; Fri, 04 Sep 2009 08:04:00 -0600 (MDT) Date: Fri, 04 Sep 2009 10:03:59 -0400 From: Kim Haase Subject: Re: Publishing the Derby documentation In-reply-to: <4AA0FCD9.4030300@Sun.COM> Sender: Camilla.Haase@Sun.COM To: derby-dev@db.apache.org Reply-to: Camilla.Haase@Sun.COM Message-id: <4AA11E4F.30507@Sun.COM> References: <4A9F94FB.60001@Sun.COM> <4AA0FCD9.4030300@Sun.COM> User-Agent: Thunderbird 2.0.0.21 (X11/20090311) X-Virus-Checked: Checked by ClamAV on apache.org A nightly build has been lovely (thanks, Myrna!) but realistically, once a week would be fine for a build of the latest docs. I wish I could volunteer for this, since I'm the one who always complains when the process breaks down, but I can't afford the time to learn about cron jobs and checksums (about which I am extremely ignorant). So many thanks to whoever takes this on. Kim On 09/04/09 07:41, Kristian Waagan wrote: > Myrna van Lunteren wrote: >> On Thu, Sep 3, 2009 at 3:05 AM, Kristian >> Waagan wrote: >> >>> Hello, >>> >>> I have now configured a Hudson job building the Derby documentation. >>> >> >> Great! >> Thanks for all your work on setting up the Hudson system. >> >> I have one question...I've a automated process that copies nightly >> built docs out to /www/db.apache.org/derby/docs/dev. Can/Should I stop >> that job? >> > > Hi Myrna, > > I think you can stop the job, but I would appreciate if you kept > everything around for a while :) > Maybe you want to test out the new script when it's ready, or integrate > it in such a way that your builds work as a backup system in case Hudson > goes down. > > The docs take a little less than 1 hour to build on the Apache server > we're using. > How often do we want to check for changes and rebuild the docs? > > The website also has some stuff that looks like old cruft to me: > /www/db.apache.org/derby/docs/10.0-bak > /www/db.apache.org/derby/docs/10.1_old > /www/db.apache.org/derby/docs/10.4_old > docs-10.0.tar > docs-10.0.tar.gz > docs-10.0.zip > > Does anyone object to deleting these? > There are also some old files lying around in dev/, so I would delete > that one too and "repopulate" it. > > > Some of the directories have wrong ownership and/or wrong permissions. I > have taken action to fix that by sending mails to Rick, Andrew and the > infrastructure team. > To allow any committer to fix issues, it is important that the > files/dirs have group ownership set to 'db' and that the group is given > write access. > >