Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of gstein@gmail.com designates
 209.85.212.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F71EEC1.6000305@wandisco.com>
References: <4F71EEC1.6000305@wandisco.com>
Date: Tue, 27 Mar 2012 13:38:51 -0400
Message-ID: 
 <CABD8fLW-pVQL2WmiSVTdQj+gvSCz02gOrt8d6+eSJbnMqODDvg@mail.gmail.com>
Subject: Re: Milestone changes on the project issue tracker.
From: Greg Stein <gstein@gmail.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 27, 2012 at 12:45, Gary <gary.martin@wandisco.com> wrote:
> Hi,
>
> I have changed the milestones in https://issues.apache.org/bloodhound to =
get
> away from the defaults that Bloodhound provides. Instead of the milestone=
N
> set we now have:
>
> =A0* "RC1 for initial release" which is self explanatory but it may be of
> interest that it specifies a tentative due date of Apr 27th.
> =A0* "Unscheduled" which is intended for work that should be done but has=
 not
> been assigned to a milestone
>
> I am also considering creating a triage milestone to go with those.

I would think of "Untriaged" as a status (eg. all new issues). Once
the issue has been triaged, then it goes into a specific milestone.

Cheers,
-g