On 2012/04/26 17:45, Ramy Yanetz <ryan...@yahoo.com> wrote: > Agree with all the comments, but just to clarify I was referring to > regressions only, which should be very few if any after each new build. I > would be happy to scan tickets for regressions after each build but I don't > find such an attribute in the trac system or a method to locate those (other > then reading through the discussions of each ticket).
Even we don't know immediately if a bug report is a regression or an old bug. Most bug reports we get are old bugs which went unnoticed for many years. That is because XCSoar has become very popular, and more pilots find more bugs, no matter if old or new ... Again: everybody can help improve XCSoar by attempting to reproduce bug reports, check the same procedure with the older version, add comments with helpful information to tickets, etc. That saves us developers time, and we will invest that time in more bug fixes and more new features. Max ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
