Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 26427 invoked from network); 10 May 2006 07:49:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 May 2006 07:49:19 -0000 Received: (qmail 66068 invoked by uid 500); 10 May 2006 07:49:06 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 65985 invoked by uid 500); 10 May 2006 07:49:06 -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 65936 invoked by uid 99); 10 May 2006 07:49:05 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 May 2006 00:49:05 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [212.23.3.141] (HELO heisenberg.zen.co.uk) (212.23.3.141) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 May 2006 00:49:05 -0700 Received: from [82.69.78.226] (helo=[192.168.0.2]) by heisenberg.zen.co.uk with esmtp (Exim 4.30) id 1FdjR6-0005CG-45 for dev@forrest.apache.org; Wed, 10 May 2006 07:48:44 +0000 Message-ID: <44619AD2.5020700@apache.org> Date: Wed, 10 May 2006 08:48:34 +0100 From: Ross Gardler User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Forrest Developers List Subject: [ANNOUNCE] Use Case suport in projectInfo plugin Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-Heisenberg-IP: [82.69.78.226] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I finally got around to implementing a the basics of Use Case documentation in the projectInfo plugin - I've been trying to find the time for this for years!!! Basically, the idea is that Use Case documentation is useful in many ways: - during design - what needs to be done - during development - what needs to be done/has been done - during use - user documentation of common activities - during maintenance - how something was implemented This is only a start - who knows when I will find time to add the extra features I want, like integration with bug trackers. Anyway, update your projectInfo plugin and take a look at: http://localhost:8888/docs/user/useCases.html and http://localhost:8888/docs/developer/useCases.html My team here are finding it really useful, but there is a long way to go. Ross