On Monday, March 11, 2013 2:33:19 PM UTC-4, Max Kellermann wrote:
On Monday, March 11, 2013 7:11:25 PM UTC+1, Evan Ludeman wrote:

I spent most of three seasons using XCS for US contests. On Ipaq 3950s to start, later on Dell Streak 5. Nine or ten contests IIRC. Something important was always busted in software. Start rules, AAT task optimizer, little things :-/. I wrote lots of trouble tickets. Some got acted on right away, some never.



Some never? The following points to a exhaustive list of all of your tickets we havn't worked on yet:



http://bugs.xcsoar.org/query?status=...%40g mail.com



This is exactly one ticket, one that can't be any less serious.



Yes, you found a lot of problems over the years (totalling 24), and that was your contribution to a better XCSoar, it helped a lot. Thousands of eyes find thousands of problems in such a complex software (nearly 26,000 users on Android alone). We do our best to deliver high quality to all those pilots, and we need input from people like you.



But please be honest. I know you want to drop some advertisement for your employer, but don't exaggerate the severity and number of open bugs.



Actually, inability to d/l waypoints to a 302 is a pretty serious defect *for me* since I use the 303 display routinely and travel to many different soaring sites (but only because the 302 has small memory and no way to manage multiple waypoint sets). Without that capability, I have to drag out a laptop, pop the canopy off to get under the panel, etc. That much of the interface was all very handy with the little Ipags that could run the Cambridge utility.

The fact remains *every* release of XCSoar I used had significant bugs that affected its utility in competition. If you've fixed some of the tickets I left behind since I bothered to look (roughly last June), thank you, perhaps it will help others.

Evan Ludeman / T8