From: Damien R. <dam...@me...> - 2012-03-05 09:12:32
|
On 05/03/12 00:11, Robert Munteanu wrote: > Recently some issues reported against 1.2.x were closed as fixed in > 1.3 or the master branches. I'm not sure whether this fits our current > approach of ( still ) supporting 1.2.x . > > My suggestion is that we not close issues reported against 1.2.x as > 'fixed in 1.3', at least until we have a consensus to retire 1.2. For me that's not a huge issue if a bug reported on 1.2.x is resolved in 1.3.x. If it's a critical issue on 1.2, it can always be back-ported. However, I do have a serious problem with marking issues as resolved+fixed, when there are no commits available in any of the "official" branches (i.e. master-1.2.x, master or even next) to back it up, and sometimes no closing comments (not to mention improperly set target/fixed in version). Just a few random examples from recent history to illustrate my point: http://www.mantisbt.org/bugs/view.php?id=11605 http://www.mantisbt.org/bugs/view.php?id=11965 http://www.mantisbt.org/bugs/view.php?id=12934 http://www.mantisbt.org/bugs/view.php?id=12796 And this one was even reopened and then closed again http://www.mantisbt.org/bugs/view.php?id=12484 I think it's bad practice to do that, because these issues then fall off the radar, and might end up never being resolved assuming there were commits made in some local branch, and that branch is never merged. On 05/03/12 03:45, Victor Boctor wrote: > The problem is when the next release doesn't ship for an extended > duration. Exactly... So, any takes on when 1.3/2.0/next/whatever will be out ? ;-) Damien |