Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of mcintyre.a@gmail.com designates
 64.233.182.193 as permitted sender)
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:content-transfer-encoding:content-disposition:references;
        b=MkT+n9d5xut0sU+UshPd/88ARYZWW/5Ngbk52yjeZPzOURrw9xG7+AD5Im2lvDt3zAm24r2XKBpdo88a1pDdsIPrFcMgf3omP5/UK1HJNpB6CpZKzCwSaN7DEuDhm0vkI5edHhFMgms5kpwWv3EW0L2LY6SrlLL3kSPkszmJ+ms=
Message-ID: <54ac72d70602281355k666639bend47841df662b93b1@mail.gmail.com>
Date: Tue, 28 Feb 2006 13:55:42 -0800
From: "Andrew McIntyre" <mcintyre.a@gmail.com>
To: derby-dev@db.apache.org
Subject: Re: Derby commit process
In-Reply-To: <44048701.1060903@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43FDE23B.60009@amberpoint.com> <43FECB56.8070102@Sun.COM>
	 <44048701.1060903@Sun.COM>

On 2/28/06, John Embretsen <John.Embretsen@sun.com> wrote:
>
> * Patch available
> * Patch reviewed
> * Patch revised
> * Patch finalized
>
> I think enabling these status items for the Derby project would improve o=
ur
> "commit process" - certainly it will reduce confusion regarding our "Patc=
h
> available" check box. Any chance these status items can be enabled for De=
rby
> (and remove the "Patch available" check box)?

Oh dear. I had been playing with the workflows in JIRA and created
some new status types, and I didn't realize that they would be
viewable anywhere in JIRA since they're not actually part of any
workflow. They can't just be 'enabled' because they have to be part of
a workflow scheme, and I didn't get around to finishing it.

The reason I didn't finish the workflow is because JIRA's workflow
editor does not allow you to insert common actions (like Resolve or
Close) into a workflow with their GUI. Instead, the XML for the
workflow would need to be edited directly to add the common actions
into the new steps. The workflows are based on the XML schema
developed by the OSWorkflow project:
http://www.opensymphony.com/osworkflow/

I don't have time to work on it at the moment. If someone was really
interested, I could dump out the skeleton workflow in XML format for
them to work on.

andrew