Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BBB309FEF for ; Sat, 9 Jun 2012 01:47:04 +0000 (UTC) Received: (qmail 67686 invoked by uid 500); 9 Jun 2012 01:47:03 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 67494 invoked by uid 500); 9 Jun 2012 01:47:03 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 67482 invoked by uid 99); 9 Jun 2012 01:47:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Jun 2012 01:47:03 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Jun 2012 01:46:56 +0000 Received: by obhx4 with SMTP id x4so3399227obh.6 for ; Fri, 08 Jun 2012 18:46:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=MJlvL4jrDDpF1Db8D/eQA4QS3sP4Ufh7r4RZ8Y9jH98=; b=eNFuC1pEkjUmH4kFpozTUP+7cz5XyhiiVxzsjsBx6Y9of70Eonxm8MZRmfihFzI0Kd DIECNgC7gGQGaUofl1x9YkGUfWf3JIeHo84CI5nGRDZhPYVE+phr6rsjHqLxxUXtVb3U z6lEETaqq9BIAld/NfFR/GGOJ+Io8JG6uT+OPVW7x1ORqApumEPZPazneaxiUaRocJ/S Wi7IPeuHIv5oHj1pdmWH8RGrploksTFr2miQyZDB0/rReRNdVwjhV3hUT/aT8DWYPQyb bZYQt6r64lRvQ9NVmYPxogu6JqKZ6zkDsWK6BfVwfEN6RAhZv7Xq+nBl2WPtbp2WGJOt NrLg== MIME-Version: 1.0 Received: by 10.182.167.39 with SMTP id zl7mr9219148obb.10.1339206394952; Fri, 08 Jun 2012 18:46:34 -0700 (PDT) Received: by 10.182.105.70 with HTTP; Fri, 8 Jun 2012 18:46:34 -0700 (PDT) In-Reply-To: <20120609013806.GC33433@igg.local> References: <20120609013806.GC33433@igg.local> Date: Sat, 9 Jun 2012 02:46:34 +0100 Message-ID: Subject: Re: Clutch data - could ReportingSchedule data be merged into podlings.xml ? From: sebb To: general@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 On 9 June 2012 02:38, David Crossley wrote: > sebb wrote: >> As the subject says: is there any need for a separate >> ReportingSchedule page now that we have podlings.xml? > > Some things to take care with, when we modify Clutch: > > Clutch based everything on the presence in ReportingSchedule > and the name of the podling used there (lowercase, no spaces). Presence is roughly equal to status=current. Clutch currently uses the same transformation on the podling name atttribute. So this should not be much of a problem. > The main name in podlings.xml might be different, > so some assumptions in clutch might need adjustment. If a name attribute in podlings.xml is wrong, then it needs fixing. AFAIK, they all agree currently (IIRC clutch checks this). > Also the sequence of its data and hint-gathering process. Yes. > So a basic entry for a podling needs to be added to > the podlings.xml file soon after acceptance. Yes. > -David > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org > For additional commands, e-mail: general-help@incubator.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org