From: Glenn H. <thr...@lo...> - 2011-07-27 00:00:16
|
At one time we did this when we weren't sure what the next release was. The intent was that when this was decided, we would move all of the issued to the new (next) version number. I've used this in other installations where the Marketing group can't decide on the name of the next release, but Engineering wants to continue to work. ... Glenn -- Glenn Henshaw Logical Outcome Ltd. e: thr...@lo... w: www.logicaloutcome.ca Mantis Developer and User since 2002 On 2011-07-26, at 12:24 PM, Damien Regad wrote: > I was wondering why we have this version "git trunk" in the tracker, > since bugs are generally reported on a released version (or in > 1.2.x/1.3.x), and then targeted/marked as fixed in 1.2.x/1.3.x > > So why do we have "git trunk", and is there a reason for keeping it ? If > not, cant it be removed from the list ? From my POV it causes confusion > as it could apply to both 1.2.x, 1.3.x (or even something else). > > Damien > > > ------------------------------------------------------------------------------ > Magic Quadrant for Content-Aware Data Loss Prevention > Research study explores the data loss prevention market. Includes in-depth > analysis on the changes within the DLP market, and the criteria used to > evaluate the strengths and weaknesses of these DLP solutions. > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |