May I use this thread to suggest that we consider tickets for 1.4 only if their *fix version* is set to 1.4? For 1.3, we have been looking at *affects version* as well as *fix version*, which in my mind doesn't make sense. An issue may be affecting 1.3 but may be fixed for 1.5 only.
This way, developers can choose the tickts that they want to work on by setting the fix version and those not associated with a fix version of 1.4 will automatically *not* be considered for this release. Tobias On 20.03.2012, at 19:44, Christopher Brooks <[email protected]> wrote: > Yup, they should all have their fix version wiped, then the RM's (and > devs) for 1.3.1 and 1.4 can prioritize what is in scope for the next > release. > > Chris > > On Tue, 20 > Mar 2012 11:25:57 -0700 Judy Stern <[email protected]> wrote: > >> Should the remaining open Affects 1.3 with Fix 1.3-only bugs be given >> a new Fix version? I just set MH-8632 (the blocker bug Kevin pointed >> us to this morning) to Fix 1.3.1 and 1.4, since it had no Fix >> version. Let me know if I did the wrong thing. >> >> Judy _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
