From dev-return-26193-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Tue Nov 28 23:57:58 2006 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 81624 invoked from network); 28 Nov 2006 23:57:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Nov 2006 23:57:56 -0000 Received: (qmail 52108 invoked by uid 500); 28 Nov 2006 23:58:05 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 52074 invoked by uid 500); 28 Nov 2006 23:58:05 -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 52063 invoked by uid 99); 28 Nov 2006 23:58:04 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Nov 2006 15:58:04 -0800 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 [65.77.211.84] (HELO www2.kc.aoindustries.com) (65.77.211.84) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Nov 2006 15:57:52 -0800 Received: from fo1.kc.aoindustries.com (www2.kc.aoindustries.com [65.77.211.84]) by www2.kc.aoindustries.com (8.13.4/8.13.4) with ESMTP id kASNv3ii014268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 28 Nov 2006 17:57:17 -0600 Received: from localhost (localhost [[UNIX: localhost]]) by fo1.kc.aoindustries.com (8.13.4/8.13.4/Submit) id kASNuePo014147 for dev@forrest.apache.org; Tue, 28 Nov 2006 17:56:40 -0600 X-Authentication-Warning: fo1.kc.aoindustries.com: indexgeo set sender to crossley@apache.org using -f Date: Wed, 29 Nov 2006 10:56:31 +1100 From: David Crossley To: dev@forrest.apache.org Subject: Re: content of release [was: Re: review list of scheduled issues for 0.8 release] Message-ID: <20061128235631.GA10992@igg.indexgeo.com.au> References: <499888440607101749p3c1ce836rb450d26187dc9eeb@mail.gmail.com> <44B2F9B4.40201@apache.org> <20061123080454.GQ903@igg.indexgeo.com.au> <456607E1.4080306@apache.org> <20061127084606.GY903@igg.indexgeo.com.au> <456B292E.10002@apache.org> <499888440611271313w5790c5f9yed54009c199afb41@mail.gmail.com> <20061128075407.GA6844@igg.indexgeo.com.au> <1164704674.5987.22.camel@localhost> <456CC47F.1010709@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <456CC47F.1010709@apache.org> User-Agent: Mutt/1.4.2.1i X-Virus-Checked: Checked by ClamAV on apache.org Ross Gardler wrote: > Thorsten Scherler wrote: > > > >Regarding the whiteboard and seeing that the dispatcher has gained wider > >community support, I think we should either move the dispatcher out of > >the whiteboard or include the whiteboard into the release. > > I'm still of the opinion that nothing in whiteboard goes into the > release. If something is stable and community oriented enough to warrant > going into the release then we should attend to it as part of the 0.8 > release cycle. > > Candidates for migration from whiteboard are, IMHO: > > - dispatcher > - forrestbot > - forrestbar > > Dispatcher looks like a given to me, in fact I've called for someone to > bring it out of whiteboard many times, if the devs active on that code > now agree it is ready then this is great news. > > Forrestbot is, in my opinion, not stable or complete enough for release > as a user tool (althoug I do have it running in a couple of locations). > David points out that we have "released" it before, but this is only as > a part of whiteboard, I don't really see that as a release since > whiteboard has always had the status of experimental and potentially > unsupported code. Both forrestbot and forrestbar are not in the whiteboard, they are in "tools".. I have been happily using forrestbot every week to publish the Forrest site, and i use it for a work-related site to efficiently publish two versions of the same site. I do not see any "stability" issues and i do not see any required new features. What do you think that it lacks? -David > Forrest bar seems very popular with devs and is a very useful tool when > trying to empower new devs. We are missing an opportunity having it > hidden away in whiteboard. Someone should bring it out (sorry, not me, > too little time right now). > > Ross