Process for providing security updates for chromium-browser

[Rick Spencer]

On Wed, 2010-08-18 at 19:21 +0200, Martin Pitt wrote:
> Hello Chris,
> 
> Chris Coulson [2010-08-18 13:38 +0100]:
> > I'm currently working on trying to get Chromium in to main for Maverick,
> 
> For the records, can you please point out why we need to have it in
> main, especially after feature freeze?
> 
> On a purely personal perspective, I have started using Chromium a bit
> for an OEM project I'm working on, and I was really amazed about some
> of its shortcomings and bugs (like a lot of crashes on particular web
> pages, or this total misconception of a configuration system). It
> seems to me that they still have some way to go until they reach
> Firefox' maturity. 
> 
> So the reason I ask is that time will obviously work in our favour
> here: in 6 months they might have stabilized their rapid development a
> bit and might make changes to their release process which might be
> more suitable for distros. (Well, I'm optimistic).

I had this specific conversation with Pat. So long as chromium continues
to get security updates in universe, it's OK to with OEM to wait for one
more release to get them into main.

Pat, are you still in agreement with that?

Cheers, Rick