Nathanael Rebsch > On 10/13/2010 10:59 AM, Vivian Meazza wrote: > > Martin Spott wrote: > > > > > >> Curtis Olson wrote: > >> > >>> On Sat, Oct 9, 2010 at 5:34 PM, Martin Spott wrote: > >>> > >>> > >>>> Hi, the page: > >>>> > >>>> http://www.flightgear.org/announce.html#v2.0.0 > >>>> > >>>> says: "Version 2.0.0 [...] is primarily a bug fix release". I don't > >>>> think this holds true ;-) > >>>> > >>>> > >>> I'm open to suggestions for more appropriate verbiage. :-) > >>> > >> Well, in case of doubt I'd probably just ask those people, who decided > >> that > >> it's been worth incrementing the major release number for this very > relase > >> - > >> they should know best ;-) > >> > >> > > This is yesterday's question. Perhaps today's question should be: "What > > should we call the next release? And when is it planned?" > > > > I think that it might be considered that the differences (at least in > the > > visual aspects) between 2.0.0 and the current Git/Head already exceed > those > > between 1.9.1 and 2.0.0. > > > > Vivian > > > Sounds to me like it would be worth investing time in finding an answer > to 'what is our release cycle' as this would answer the 2 questions: > 'what is the next release' (in terms of version numbering) and also > 'when is it planned' >
It might be appropriate to consider the idea of a "release engineer2 who is not one of the principle developers to draw up and execute a plan for the release cycle. Vivian ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
