20,741
edits
Release plan: Difference between revisions
→August 2013
m (→2.6) |
|||
| Line 217: | Line 217: | ||
Once we clear past the 2.10, 2.12, etc. series, I'd like to go back to keeping things single digits in the major and minor version numbers and when we run out of a single digits bump up the major number (so 3.8.x -> 4.0.x). Number are numbers, but this one confused a lot more people than I expected it would or should so maybe it's good to be sensitive to that after we clear the 2.x series of versions.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40358.html|title=<nowiki>Re: [Flightgear-devel] reminder: entering feature freeze now</nowiki>|author=Curtis Olson|date=Tue, 25 Jun 2013 14:59:08 -0700}}</ref>|Curtis Olson}} | Once we clear past the 2.10, 2.12, etc. series, I'd like to go back to keeping things single digits in the major and minor version numbers and when we run out of a single digits bump up the major number (so 3.8.x -> 4.0.x). Number are numbers, but this one confused a lot more people than I expected it would or should so maybe it's good to be sensitive to that after we clear the 2.x series of versions.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40358.html|title=<nowiki>Re: [Flightgear-devel] reminder: entering feature freeze now</nowiki>|author=Curtis Olson|date=Tue, 25 Jun 2013 14:59:08 -0700}}</ref>|Curtis Olson}} | ||
{{cquote|I think I sensible step in that case is to keep 3.0 as backward compatible (in terms of Aircraft APIs) with 2.12 as possible, which mostly means my resisting the urge to clean up legacy stuff :) | |||
Obviously it's tricky to offer a 100% guarantee, but I don't have anything planned for 3.0 that will require aircraft changes - I'm sure new technologies | |||
such as state machines, knob/slider animations and tooltips will mature and gain some new features but hopefully aircraft developers will be able to work | |||
against 2.12 with confidence that things will work the same in 3.0<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40366.html|title=<nowiki>Re: [Flightgear-devel] reminder: entering feature freeze now</nowiki>|author=James Turner|date=Wed, 26 Jun 2013 02:49:00 -0700}}</ref>|James Turner}} | |||
{{cquote|It's a bit tricky because I haven't had much feedback from aircraft developers about the new APIs (since they aren't in 2.10), but once 2.12 ships we would want to keep them compatible, so fingers crossed the current design is sensible <ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40366.html|title=<nowiki>Re: [Flightgear-devel] reminder: entering feature freeze now</nowiki>|author=James Turner|date=Wed, 26 Jun 2013 02:49:00 -0700}}</ref>|James Turner}} | |||
==== 2.10 ==== | ==== 2.10 ==== | ||