Ok, I know it's work and it's boring. How about release candidates? After finishing a major version (e.g. 6.4) publish it as XCSoar-testing and ask users to test it in their environment with their devices. If users cooperate they will probably catch most of the "serious" and "medium" bugs. It shouldn't be much more work than now. Just tell us that it's a release candidate and let us test it for two weeks. If nothing serious appears, let it be the release. Be a little more conservative if possible, withouth adding too much boring work for developers.
Just my $0.02, Tibor On Tue, Apr 24, 2012 at 17:49, Max Kellermann <m...@duempel.org> wrote: > On 2012/04/24 15:05, Tibor Arpas <ti...@bidforfix.com> wrote: >> But most of the time I prefer stability and reliability over new >> featers in my gliding computer. Is that just my taste? What do the >> developers think about a "long term support" version? > > We don't have the resources to maintain a second stable branch. It's > really boring work, 90% of which I have to do myself. Maintaining an > even older branch is just more boring, with only few users and no > future. > > We try our best to keep one stable branch with regular bug fix > releases. We cannot ultimately preclude regressions. > > Every one of you can help make XCSoar more stable by taking time and > test it with replays, verify calculations, and writing bug reports, > responding to questions we have. I'm glad that this works well > already. > > 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
