From dev-return-25551-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Thu Aug 24 03:27:44 2006 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 40564 invoked from network); 24 Aug 2006 03:27:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Aug 2006 03:27:44 -0000 Received: (qmail 23502 invoked by uid 500); 24 Aug 2006 03:27:44 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 23350 invoked by uid 500); 24 Aug 2006 03:27:43 -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 23339 invoked by uid 99); 24 Aug 2006 03:27:43 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Aug 2006 20:27:43 -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 [65.77.211.84] (HELO www2.kc.aoindustries.com) (65.77.211.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Aug 2006 20:27:42 -0700 Received: from www2.kc.aoindustries.com (www2.kc.aoindustries.com [65.77.211.84]) by www2.kc.aoindustries.com (8.13.1/8.13.1) with ESMTP id k7O3RHBC011699 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Aug 2006 22:27:17 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by www2.kc.aoindustries.com (8.13.1/8.13.1/Submit) id k7O3RGr7011621; Wed, 23 Aug 2006 22:27:16 -0500 X-Authentication-Warning: www2.kc.aoindustries.com: indexgeo set sender to crossley@apache.org using -f Date: Thu, 24 Aug 2006 13:27:09 +1000 From: David Crossley To: dev@forrest.apache.org, brightoncomputers@brightontown.com.au Subject: Re: [RT] A new Forrest implementation? Message-ID: <20060824032709.GT25736@igg.indexgeo.com.au> References: <20060823070851.GK25736@igg.indexgeo.com.au> <000901c6c6ae$08564b00$0200a8c0@developer> <20060824014550.GS25736@igg.indexgeo.com.au> <1092.124.168.75.181.1156386209.squirrel@webmail.e-wire.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1092.124.168.75.181.1156386209.squirrel@webmail.e-wire.net.au> User-Agent: Mutt/1.4.2.1i X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Gav... wrote: > > > Gav.... wrote: > >> > >> Just on a year a go, a Jira Issue was set up entitled 'Forrest Strategy > >> and > >> direction' - seems appropriate to revisit that issue and see what ideas > >> there have been dealt with, what we still need to deal with and what we > >> can > >> drop. > >> > >> http://issues.apache.org/jira/browse/FOR-630 > >> > >> (Strange how a jira issue of Critical Priority is also unscheduled, just > >> seems a little odd to me) > > > > We can only schedule an issue to be fixed before the > > next release when there is something to be actually done. > > That FOR-630 is just a bag of notes. I reckon that we have > > already extracted any that really need to be done for > > the 0.8 release. > > Ok, so do you think it should be closed? No. It has other stuff beyond 0.8 that is not yet attended to. > > Perhaps there are more, but really we are trying to trim > > the list down, rather than find more :-) > > Absolutely, I thought it relevent to this thread so just > thought it worth a mention, otherwise why have it in the > Jira for a year sitting there and not being useful. So that people can get frustrated by it and eventually do something about it. Only partially joking. I reckon that is is still useful. Some more of the items need to eventually be split off into their own issues. I say eventually because i am desperately trying to focus us on the release. > You may have noticed I just started to go through some of > the unscheduled issues to see if any could be revisited, > fixed, closed or left as is. As has been pointed out before > users (that term again) get disheartened to see their issues > sat there not been looked at, even if just to comment on it. > > And I like tying up loose ends if possible :) I fully agree with you. It is an opensource downer when one's contributions are not followed up. However, we need to look at the flip-side. Perhaps it would be better to let them wait a bit longer. If you, Gavin, have time to attend to general stuff, then it would probably be better spent focussing on the currently scheduled issues. Other committers have already tried a few times to look at the unscheduled list. Looking at it again means we need to respond to your questions, and so cannot attend to other stuff. -David