Points taken, Max. And thanks for adding that multitouch support for panning,
which was a big improvement for Android devices. I am using it all the time.
The timeline feature looks handy, thanks Tiurbo for pointing it out.
I offered before to help with prioritizing bugs and enhancements, but the
response was that developers prefer to prioritize themselves based on
complexity and personal preference, or something like that...
If my coding skills were not rusted I would have been more than happy to
develop fixes and enhancements.
So the best I can do for now is bug reporting and enhancement suggestions to
try to make XCSoar even better.
Thanks,
Ramy
>________________________________
> From: Max Kellermann <m...@duempel.org>
>To: Ramy Yanetz <ryan...@yahoo.com>
>Cc: "xcsoar-user@lists.sourceforge.net" <xcsoar-user@lists.sourceforge.net>
>Sent: Tuesday, June 26, 2012 1:26 PM
>Subject: Re: [Xcsoar-user] Latest XCS-test on Android fails at startup
>
>On 2012/06/26 22:05, Ramy Yanetz <ryan...@yahoo.com> wrote:
>> Max, thanks for the url. It is indeed handy, but returned 82 matches. Trying
>> to locate potential new regressions in this list is not that simple. Note
>> that I was referring only to serious bugs and potential regressions, not
>> every bug report.
>
>That's simple. Click on the "Priority" column and see the list sorted
>by priority:
>
>http://www.xcsoar.org/trac/query?status=accepted&status=assigned&status=new&status=reopened&type=defect&order=priority
>
>Now if only people would fill "priority" in a way that would make
>sense for us. Not like this one:
>
>http://www.xcsoar.org/trac/ticket/1555
>"Need multitouch support for Android devices", "Priority: highest"
>
>Tickets like this one are the reason we tend to ignore the "priority"
>field.
>
>> Why sharing serious bugs and potential regressions on this list will be
>> considered spamming?? I don't expect many of those anyway. I think this is
>> the right place to share with others issues which may impact others.
>> Otherwise, perhaps I misunderstood the purpose of this mailing list?
>
>I consider this spamming because this is not the place to discuss bug
>reports. We have a dedicated place for that (i.e. the bug tracker).
>
>But if you feel it's necessary, we can create a new mailing list, for
>announcing regressions, managed and moderated by you. Anybody who's
>interested may subscribe.
>
>If you want bugs to be fixed quickly, come up with something that
>saves developer's time, so they can spend more time on bug reports.
>Recruit new developers[*], help us manage the bug tracker or the web
>site, assign priorities, raise donations to buy test hardware for
>developers[**], explain to people how they can extract a logcat, or
>better: write manual pages, ...
>
>There's a never-ending list of things *you* can do to accelerate
>XCSoar development and bug fixes.
>
>[* new volunteers may implement your favorite feature requests or fix
>important bugs - convince somebody to spend time on your requests]
>
>[** many bugs cannot be fixed because no developer owns the product
>that fails, e.g. http://www.xcsoar.org/trac/ticket/2154 - there's
>nothing we can do until we have this product]
>
>
>
------------------------------------------------------------------------------
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
