Return-Path: 
 <dev-return-11228-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org>
Delivered-To: apmail-forrest-dev-archive@www.apache.org
Received: (qmail 55112 invoked from network); 18 Jul 2004 14:27:11 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 18 Jul 2004 14:27:11 -0000
Received: (qmail 82589 invoked by uid 500); 18 Jul 2004 14:27:10 -0000
Delivered-To: apmail-forrest-dev-archive@forrest.apache.org
Received: (qmail 82568 invoked by uid 500); 18 Jul 2004 14:27:10 -0000
Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@forrest.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@forrest.apache.org>
list-post: <mailto:dev@forrest.apache.org>
Reply-To: dev@forrest.apache.org
Delivered-To: mailing list dev@forrest.apache.org
Received: (qmail 82553 invoked by uid 99); 18 Jul 2004 14:27:10 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received: from [65.77.211.93] (HELO indexgeo.net) (65.77.211.93)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Sun, 18 Jul 2004 07:27:06 -0700
Received: from [192.168.1.100] (dsl-109.227.240.220.dsl.comindico.com.au
 [220.240.227.109])
	(authenticated bits=0)
	by www2.kc.aoindustries.com (8.12.9-20030917/8.12.9) with ESMTP id
 i6IER19H010851
	for <dev@forrest.apache.org>; Sun, 18 Jul 2004 09:27:03 -0500
Subject: Re: [PMC] How to maintain status.xml
From: David Crossley <crossley@apache.org>
To: dev@forrest.apache.org
In-Reply-To: <cdds9h$8a3$1@sea.gmane.org>
References: <cdds9h$8a3$1@sea.gmane.org>
Content-Type: text/plain
Organization: 
Message-Id: <1090160810.1668.53712.camel@ighp>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) 
Date: 19 Jul 2004 00:26:51 +1000
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Scherler, Thorsten wrote:
> I just wondered whether we have guidelines to maintain the status.xml? I 
> could not found anything at: http://forrest.apache.org/contrib.html
> 
> New entries go into the top after:
> 
>      <release version="0.6-dev" date="unreleased">
>        <action dev="DC" type="add" context="docs">
>        <!-- Please keep this action at the top -->
>          Added new document to facilitate
>          <link href="site:upgrading_06">upgrading to v0.6</link>
>        </action>
> <!-- in lifo order -->
> <new/>

The best thing is just to follow examples of other entries.

The @type attribute causes the issues to be sorted into groups
on the changes.html page.

If there is a contributor, then add their name in the
@due-to attribute. They should also be acknowledged in
the 'svn commit' message when their files were committed.

We never put their email address in plain text, only in the
@due-to-email attribute which will get obfuscated. Sometimes
we don't even show their email address at all.

Add the issue number in the @fixes-bug attribute.

You are right though, we do need some written guidelines.

-- 
David Crossley