From dev-return-27837-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Wed Jun 06 23:11:55 2007 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 62463 invoked from network); 6 Jun 2007 23:11:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Jun 2007 23:11:53 -0000 Received: (qmail 48311 invoked by uid 500); 6 Jun 2007 23:11:57 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 48149 invoked by uid 500); 6 Jun 2007 23:11:56 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 48138 invoked by uid 99); 6 Jun 2007 23:11:56 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jun 2007 16:11:56 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [66.111.4.25] (HELO out1.smtp.messagingengine.com) (66.111.4.25) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jun 2007 16:11:51 -0700 Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 8689D2318DB for ; Wed, 6 Jun 2007 19:11:30 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Wed, 06 Jun 2007 19:11:30 -0400 X-Sasl-enc: ndVwAS7qH7AkWEZSr9SYf6A9Ud1jc0bxuDPOGqKwyfsO 1181171489 Received: from localhost (dsl-41-216.nsw1.net.au [125.168.41.216]) by mail.messagingengine.com (Postfix) with ESMTP id 2DD561C710 for ; Wed, 6 Jun 2007 19:11:28 -0400 (EDT) Date: Thu, 7 Jun 2007 09:11:24 +1000 From: David Crossley To: dev@forrest.apache.org Subject: using status.xml files for changes notes Message-ID: <20070606231124.GD540@igg.indexgeo.com.au> References: <61c9bc470706060642j58ce8896g5b74482ddc074813@mail.gmail.com> <61c9bc470706061450u3eb8980em8745774faf918f7e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <61c9bc470706061450u3eb8980em8745774faf918f7e@mail.gmail.com> User-Agent: Mutt/1.4.2.2i X-Virus-Checked: Checked by ClamAV on apache.org Ross Gardler wrote: > > Firstly, and perhaps most importantly, you must keep status.xml up to > date. There are a number of reasons for this: > > - it's how we generate the changes file and that's how our users > figure out whether or not to upgrade > - it's how you and other developers are credited with contribution to the > plugin > - it's how developers understand what is happening in the code > - it forms part of the documentation (especially at release time) Likewise it is important to also add an entry to the top-level site-author/status.xml to alert to Oshani's contribution. This gets the contributor's name into the general release notes. I just now followed up to do that. As Ross said, general changes for this plugin go into its local status.xml file. -David