XCSoar / LK8000

On Mar 27, 3:40*am, Max Kellermann wrote:
On Wednesday, March 27, 2013 4:02:11 AM UTC+1, Ramy wrote:
Having said that, if you would like to see improvement in XCSoar flarm support, you may want to add your comments and feedback to the existing tickets, or create new ones, this may attract more attention from the developers.

Agree. Our bug tracker is the way to express wishes:http://bugs.xcsoar.org/newticket

Posting on RAS may or may not be seen by a XCSoar developer. On the bug tracker, you get feedback by email whenever a developer updates the ticket status, and you can subscribe to existing tickets.

(Ramy: I know your FLARM tickets, but it won't fit in XCSoar 6.6. Some of it needs some more refactoring of the internal FLARM traffic storage.)

Yes, I saw the tickets. They were downgraded to low priority and that
was the reason I posted here as I saw Max reacting to over requests.
Ramy created a couple of tickets and I did not see anyone really
responding to those tickets so I gave up.

On Wednesday, March 27, 2013 3:05:17 PM UTC+1, Andrzej Kobus wrote:
Ramy created a couple of tickets and I did not see anyone really
responding to those tickets so I gave up.

Don't give up just yet. XCSoar 6.5 was a major milestone for us: after 4 years of code cleanup, the XCSoar code base is finally "ready". Now we can focus on features, we can start to process all the tickets people have submitted.

Just look at the XCSoar 6.6 changelog (work in progress), these are the features that were implemented after only 3 weeks:

http://git.xcsoar.org/cgit/master/xc.../tree/NEWS.txt