On 18/06/2012 18:44, Tobias Bieniek wrote: > The point of our stable branch is to release only versions with > bugfixes on it. That means that unless a bugfix reveals another bug > the next version should always be more stable than the previous one.
With open source software, there is always a dilemma as to whether to upgrade to a new version, or to stick with the bugs that you know. However one of the unwritten rules for open source software, is before you submit a bug report, you must make sure that you are running the latest appropriate version and that you can reproduce the bug on that version. In a soaring environment, sometimes this can be logistically challenging. Perhaps in this situation, there is scope to report a potential bug but to hold back on the formal report until you can do the homework. > Unfortunatly there are times where this has happened and we are sorry > for that, but we strongly recommend updating once a new maintenance > update is released. But when a bug appears after an upgrade, either with a maintenance release or with a development release, I think the developers will be keen to here about it, sooner rather than later. Of course most of us won't be flying with development releases, unless the objective of the flight is related to the software rather than some other soaring goal. Ian ------------------------------------------------------------------------------ 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
