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).
Ramy On Apr 26, 2012, at 1:41 AM, Max Kellermann <m...@duempel.org> wrote: > On 2012/04/26 09:17, Ramy Yanetz <ryan...@yahoo.com> wrote: >> May I suggest that whenever a regression is introduced, it will be published >> by XCSoar developers on this mailing list as soon as it is discovered, so we >> can decide if we rather wait for the next build or not? > > Will you volunteer for doing that? Anybody can search the bug tracker > for new bug reports. It does not need a developer for this. > > (Agree with Sascha) > > The XCSoar project has grown very large recently (more than 12,000 > pilots on Android alone!). Fortunately, we have quite a few > developers on the team, but I would like them to develop, and leave > non-development tasks to other volunteers: manage web site, coordinate > bug reports, communication with hardware vendors, user support, > translation, documentation, and so on - a never-ending list which > requires a never-ending list of volunteers :-) > > 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
