Why it's a lot of work?
Posted Jul 25, 2010 12:32 UTC (Sun) by khim
In reply to: It's easy...
Parent article: Release Early, Release Often (The Chromium Blog)
So there's no real way of figuring out whether this is a regression in chrome or a regression in my code, short of somehow keeping imprisoned old versions of chrome, which would be a lot of work to set up.
What's so hard about it? You just test with particular release of a nightly build and keep this version around for regression testing. And if it's bug in Chrome then you can create test, report it and when it's fixed in trunk you can safely assume it'll be fixed for all users in about 3 months time... while with other browsers you must keep workarounds forever.
to post comments)