On Mon, Dec 14, 2009 at 12:03 PM, Ed Burns <Ed.Burns@sun.com> wrote:
DA> On Dec 11, 2009, at 18:20, Dan Allen <dan.j.allen@gmail.com> wrote:

DA> Can we get an MR milestone in the issue tracker? Currently there is only
DA> 2.0 and 2.next. But there are issues which need to be filed against the MR
DA> (of course you can call which issues are allowed in there, but I think we
DA> still need the milestone).

DA> On Sat, Dec 12, 2009 at 1:18 AM, <Ed.Burns@sun.com> wrote:

EB> Sure, I'll add that next week.

I've added milestones for 2.1 - 2.4.  I've deleted 2.next.

It was fun while it lasted (I say that jokingly because it we were having a fun play on words with JSF 2.next ;))
 
What about 2.0.MR1? Could you add that for the errors we need to have fixed for the MR?

Instead of
2.next, we should use "unscheduled" as the target milestone if we don't
know the target milestone.

I've deleted the 2.next target milestone field and moved all issues in
it to "unscheduled".


Hmm, I'm thinking that now we need to go through the unscheduled issues and put them back into something concrete like 2.1, 2.2, etc. Because unscheduled implies they don't apply to any one of the new markers. And some of them really to apply to 2.1.

-Dan

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen