You only should maintain a certain codebase if there is a business case
for it. If your biggest customer would only use IE6 and is willing to
pay for maintaining the codebase, then do so.
However, given the dwindling number of IE6 installations (and which will
be actively migrated by MS in the next months to a higher version) I
would stop investing in a codebase which will most probably not generate
enough revenues to justify the maintenance of that code. Sometimes you
have to be prepared to say sayonara to a customer if the business case
is not there (anymore).
My 2c, Erick
______________________________________________________________________
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
