From: Victor B. <vi...@fu...> - 2012-03-05 02:45:53
|
Do you mean "resolved" or "closed"? We typically only close issues once the release has shipped. Typically it's OK to resolve issues as fixed in the next release. The problem is when the next release doesn't ship for an extended duration. On Sun, Mar 4, 2012 at 3:11 PM, Robert Munteanu <rob...@gm...>wrote: > Hi, > > 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. > > Robert > > -- > Sent from my (old) computer > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > |