Hi Judy, > I was reviewing fix version 1.2.1 bugs and became concerned that even > if these were fixed for 1.2.1 (which I'm not even sure is still on > the horizon), that they might never get fixed for anything beyond
It is; we're going to use 1.2.1 in January. Goal is for a pretty tiny maintenance release to just fix the critical bugs I think. > 1.2.1. Now, I didn't dare add 1.3 as a fix version to all of them > (figured somebody would kill me after our conversation in today's > meeting), but I did do a bulk edit and added "Trunk" to the fix > version. I hope I did the right thing (consulted with Adam first but > if it's wrong don't blame him); if there's a reason I shouldn't have > done that, let me know and I'll put 'em back to just 1.2.1 (without > the "trunk"). I would move them to 1.3 if they are 1.3 bugs as well. If they just don't get fixed before the release that's not so bad. I realise it's not always obvious if they are 1.3 bugs too though, so in that case I would leave them at 1.2.1 or trunk. Greg/Rudiger, do you know of someone who might be able to try and verify the 1.2 bugs? It sure would be good to know if they effect 1.3. If so, by marking them as 1.3 it will at least let people in the community know not to report a duplicate bug. Chris _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
