On Sat, 2012-03-03 at 22:52 +0000, Stuart Buchanan wrote:
> On Sat, Mar 3, 2012 at 1:36 PM, Erik Hofman wrote:
> > Personally I would think adding Project Rembrandt will call for
> > FlightGear version 3.0. So if it is added I would create two branches,
> > version 3.0 and version 2.7 in which the later is switched to bug fixes
> > only.
> 
> Surely a bug-fix 2.7.0 branch is simply just the 2.6.0 maintenance branch?
> 
> I'm not aware of any significant development on next so far beyond
> RTI from Matthias and some materials work that I've been doing.

That's the idea indeed. just take what is in next now and push it into
bugfix only mode.
> 
> > If 3.0 turns out to require more time than expected (I probably know the
> > answer to that one) then there's always a really stable version 2.8
> > which can be released.
> 
> Sounds like a reasonably plan, but let's aim for success :)

I probably should have specified that 3.0 (I realized later it is
actually 2.9) will be called 'next' in git :)

Erik


------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to