Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 10420 invoked from network); 18 Dec 2009 17:38:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Dec 2009 17:38:19 -0000 Received: (qmail 69608 invoked by uid 500); 18 Dec 2009 17:38:18 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 69503 invoked by uid 500); 18 Dec 2009 17:38:18 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 69492 invoked by uid 99); 18 Dec 2009 17:38:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 17:38:18 +0000 X-ASF-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of robert.newson@gmail.com designates 209.85.212.187 as permitted sender) Received: from [209.85.212.187] (HELO mail-vw0-f187.google.com) (209.85.212.187) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 17:38:11 +0000 Received: by vws17 with SMTP id 17so997141vws.13 for ; Fri, 18 Dec 2009 09:37:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=VgCcjk87RA+TRiimNQx4JkCuBi3sVLOGmtC50brQnUc=; b=jqk64e1MvBYZ4XRqyBz8iiVjT8J5uxClgYhr9ioqBF0hmNoUhVmrhUa+jvND/IjCZ1 oPQEPIjpEI4anw7N8yPlTfAoN0or9PSpXblZq9Rx17rftvgNV72/xQCena2vzioiyQW+ pKbakc1OdoSLJThqWbh6mhIRt0nlz9Ry0rGkQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=XzjMLhyQQSqtMAe8k1m4CqI7gcOi88waQkI49rmVh5CmkFdlHrv9EcRxIdBaFdNDfe dg0Hqt1ICQjjneWqaFI0qfbVmem5rf5RVed7YTrW+Lh03WzRYfEY479n26lJRaAJSRUp dKqKaETannHGZa/1BCg0aJu5lfrRrE4orggPo= MIME-Version: 1.0 Received: by 10.220.127.2 with SMTP id e2mr2969645vcs.10.1261157870313; Fri, 18 Dec 2009 09:37:50 -0800 (PST) In-Reply-To: References: <20091208114858.12390iehu02ir2fs@webmail.df.eu> <69EEF0C9-6179-4E96-A84E-54D1105AF0AB@tumbolia.org> Date: Fri, 18 Dec 2009 17:37:50 +0000 Message-ID: <46aeb24f0912180937x2b83c241p35ab55a52270aef3@mail.gmail.com> Subject: Re: Updating the CouchDB roadmap From: Robert Newson To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Jira does build a roadmap for you, but it depends on you filing bugs/tasks and assigning them as "fix for ". I'm not sure we all can add new versions (that should be locked down if it's not already), but that's how roadmaps are handled in jira. B. On Fri, Dec 18, 2009 at 5:10 PM, Paul Davis wrote: > Link might be handy: > > http://forrest.apache.org/forrest-issues.html > > On Fri, Dec 18, 2009 at 12:09 PM, Paul Davis > wrote: >> On Fri, Dec 18, 2009 at 12:05 PM, Noah Slater wrote: >>> Hey, >>> >>> Does JIRA have a page what we could use as the roadmap? >>> >>> That would have the added advantage of updating itself automatically as we edited tickets. >>> >>> I found the roadmap tab from the main CouchDB page, but it doesn't have any tickets for post 0.10 on it. >>> >>> Thoughts? >>> >>> Thanks, >>> >>> Noah >> >> There was that one page that listed tickets in a format that you said >> you were going to include in the release procedure. That's about all I >> can think of other than saving a query which isn't nearly as awesome. >> >> There's also an example from the Apache Forrest site [1] that lists >> open issues for the next release on their site which might also be an >> interesting approach. >> >> HTH, >> Paul Davis >> >> Paul Davis >> >