Well, GP team knows that we need to convert the current (old) UFO to the so-called new look-and-feel UFO. I personally think the new look-and-feel sucks big time. It is confused, complicated and filled with superfluous configuration. Yeah, one of the statements got repeated time after time at the company is "configurable". True, it's only configurable after *you* spending weeks on writing codes for the damned configurations which is mostly in XML format.
I made an estimate of 6 to 8 weeks for the conversion. And remember at the same time, we all have to take the new release development cycle into consideration. Also we have to take into account that the new UFO will "contribute" a tons of pleasingly surprise sweet bugs!!! We encounter about 2 - 4 so far during the trial period.
This reminds me of one of the most basic principle in software development: new features or enhancements must be backward compatible with the old codes. If you cannot make it compatible with the old codes then please don't coin it with the same name as the old framework, only different by the version number.
Should I quote one of the famous quote of software development principle in its parody:
"Human brain should be open for extension but close for modification"
If all fail, this is what depicts the reason of that failure: