Comment 9 for bug 851691

Revision history for this message
David Barth (dbarth) wrote :

It *is* late I won't disagree with you.

I would argue that the the scope of changes is limited to a component that essentially contributes further results to a search query, so it is not an invasive change. In its absence the system will work. In its presence there can be a few more results.

Technically, it is also rather contained, in a separate process, can be uninstalled easily. It can even be removed from the release if needed by de-listing sub-package.

There is the business factor which should be taken into account. Its positive impact would seem to outweigh the risks associated with the limited scope of change in my opinion. But that is up to the release team to judge. I'm mostly the messenger ;)

And again, I think the contingency plan is rather clear and simple: deinstall if that breaks, don't ship if pre-release reports are negative.