RedHat is eager to see Ghost development move forward, at least concurrently with everything else. Our feeling was that the surround work was more directly applicable to Ghost work than an AoTuV tuning merge, so that bumped ahead of AoTuV in the development line.
AoTuV merges take time, they're not simple patch and release situations. I'm guessing a merge is about two full-time weeks minimum, primarity because listening testing is not something that can be sped up by 'working smarter'. Even automated regression testing eats days at a time.
But it is still happening. It just didn't happen in 1.3.0/1
Re: What about the aoTuV merges?
Date: 2010-03-26 09:11 pm (UTC)AoTuV merges take time, they're not simple patch and release situations. I'm guessing a merge is about two full-time weeks minimum, primarity because listening testing is not something that can be sped up by 'working smarter'. Even automated regression testing eats days at a time.
But it is still happening. It just didn't happen in 1.3.0/1