Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 52684 invoked from network); 7 Aug 2006 15:24:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Aug 2006 15:24:30 -0000 Received: (qmail 5051 invoked by uid 500); 7 Aug 2006 15:24:26 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 5014 invoked by uid 500); 7 Aug 2006 15:24:26 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 5002 invoked by uid 99); 7 Aug 2006 15:24:26 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Aug 2006 08:24:26 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of gnodet@gmail.com designates 64.233.182.187 as permitted sender) Received: from [64.233.182.187] (HELO nf-out-0910.google.com) (64.233.182.187) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Aug 2006 08:24:25 -0700 Received: by nf-out-0910.google.com with SMTP id l36so2389176nfa for ; Mon, 07 Aug 2006 08:24:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=colIAss66wy3lRQPgBgZsxZrUMYT4HdQWWB+1wpOyGogDEGjxkKvI+eEDYkhXa3W7j0hjKMLyQtcbo7FLXM8OdGCpFewFnFJGgtvrmSCZPq9vk19I9jS5mMOlveWn6UQremTHNhJk+541/nUFHGXcQJJOtlDoT2k9uIBsqW2OpU= Received: by 10.49.26.18 with SMTP id d18mr2231913nfj; Mon, 07 Aug 2006 08:24:03 -0700 (PDT) Received: by 10.49.37.4 with HTTP; Mon, 7 Aug 2006 08:24:03 -0700 (PDT) Message-ID: Date: Mon, 7 Aug 2006 17:24:03 +0200 From: "Guillaume Nodet" To: dev@geronimo.apache.org Subject: Re: Geronimo RTC Workflow Scheme v2 In-Reply-To: <44D75323.1070704@toolazydogs.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_42772_24853357.1154964243590" References: <44D75323.1070704@toolazydogs.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_42772_24853357.1154964243590 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I think that dblevins changed that, because in XBean, I had a "Wish" for which i provided a patch but was unable to put it in RTC mode. RTC should also be applied to documentation, so why were these issue types excluded from the workflow ? I think the main problem is that you can not easily recategorize issues if they do not have the same workflow. On 8/7/06, Alan D. Cabrera wrote: > > Previously, this was set up so that only new features and improvements > followed the RTC flow. Now, this new scheme includes all issue types. > Does anyone know why this was changed? > > > Regards, > Alan > > > -- Cheers, Guillaume Nodet ------=_Part_42772_24853357.1154964243590 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I think that dblevins changed that, because in XBean, I had a "Wish" for which i provided a patch but was unable
to put it in RTC mode.  RTC should also be applied to documentation, so why were these issue types excluded
from the workflow ?
I think the main problem is that you can not easily recategorize issues if they do not have the same workflow.

On 8/7/06, Alan D. Cabrera <list@toolazydogs.com> wrote:
Previously, this was set up so that only new features and improvements
followed the RTC flow.  Now, this new scheme includes all issue types.
Does anyone know why this was changed?


Regards,
Alan





--
Cheers,
Guillaume Nodet ------=_Part_42772_24853357.1154964243590--