Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Thu, Apr 22, 2010 at 03:12:56AM +0200, Alexander Sack wrote:
> On Wed, Apr 21, 2010 at 10:14:59PM +0200, Giuseppe Iuculano wrote:
> > I don't received any answer, so I'm going to take over this ITP in order
> > to get chromium-browser in time for squeeze.
> >
> > I requested an alioth group, feel free to join it when it will be accepted.
>
> Dude,
>
> The problem is that chromium browser cannot be maintained in a debian
> stable relase as it is. If you think different talk to me on IRC.
>
> Let's wait how bad it blows up once ubuntu lucid enters stable release mode.
>
Just for the record, I don't want to stand in anyones way; however, the package
is as ready as it can be; the problem is really on upstream release process.
It's completely unclear when to release and what to release and that is what
we are trying out in ubuntu lucid. Most likely we will get out of this that
we need to work with upstream on something better.
One example: If you look at the release channels, you will notice that
there are two releases a week in average or something. Not real releases,tags
or anything like that. The problem here is that chromium uses a continuous rollout
and backout approach, which is fine on its own, but when it comes to reflecting
this in a distro you easily become trapped to either keep up with their update
frequency through the security channel :-P (e.g. going through security twice
a week ;)) ... or somehow figuring how to bake stable releases from a continuous
head in a way that you can release regression free security updates as those
are announced.
I am not saying there is no way to do that, just that its tough and we have to
learn a lot before we can consider putting chromium in a stable release for
debian.
- Alexander
Reply to: