garvinhicking wrote:I'm up for discussion on this, but personally I would prefer to make 2k11 the new template in 2.0 only, mostly to have a 1.7 version that runs as stable as possible while we introduce possible errors in 2.0; since 2.0 might be in a whacky state for some time, I wouldn't like to have another Baustelle in 1.7 as well. Even though I fully trust that 2k11 is ready for primetime I think it might raise support issues and other trivial problems that could divert our attention...
Happy Christmas to all of you!
What kind of problems do you have in mind, Garvin? Well, apart from the need to take over the bulletproof/admin backend (else it would fall back to old default/admin), it has nearly no influence to break something, IMHO. If someone has stuck with bulletproof as the default template in the past, that would not change if 1.7 arrives with a new defaultTemplate set, would it? That would only happen to new installations, or am I wrong with that?
I expect changing 1.7 to 2k11 now as a good idea, since the Smarty3 upgrade has influences to the frontend also, while draft 2.0 modifications are backend only as of now. "Raising support issues and other trivial problems" is daily business in my eyes.
And... to come up in 2013/14 with a new template from 2011, is quite "debianesque".