Mailinglist Archive: opensuse-project (205 mails)
| < Previous | Next > |
Re: [opensuse-project] Chromium package in openSUSE releases
- From: Markus Slopianka <markus.s@xxxxxxxxxxx>
- Date: Thu, 24 Nov 2011 15:01:32 +0100
- Message-id: <201111241501.32264.markus.s@kdemail.net>
On Donnerstag 24 November 2011 14:27:02 Pavol Rusnak wrote:
My experience differs and considering that the alpha snapshots are completely
untested,
the situation can change from one day to another.
No, it's not. The situation is and was: *Untested snapshots* of any software.
It's not like KDE Network Management which during Factory development in
previous releases
got a single git snapshot and that was then stabilized for release. (Whereas
untested
snapshots of that are put in KDE:/Unstable)
Here the situation is that on a weekly basis untested snapshots are delivered
as regular
updates for openSUSE.
The Chromium package carries a large number of additional SUSE patches. I don't
see them
being sent to Google...
properly
maintain its current stable release?
If the beta branch (currently 16.x) was just mere days away from becoming the
stable
release, yes, I'd agree with you.
That said, if openSUSE at least moved to ship the beta versions, one could at
least argue
that it is already a stabilization branch and at least somewhat tested.
My main argument was and is openSUSE's release process and that it does not
permit
untested snapshots of any software to be included. So far nobody refuted that
argument --
neither here nor in the bug report.
I'm open to actual arguments and how and why the openSUSE's release process
would actually
prefer untested snapshots over release versions. So far I've only read 'You are
mean to
Raymond', 'I like Chromium', and 'The web moves fast'. So far no argument at
all about
openSUSE's release process policy.
Markus
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
To contact the owner, email: opensuse-project+owner@xxxxxxxxxxxx
My take is that chromium 15.x.x.x is no more stable than chromium
17.x.x.x,
My experience differs and considering that the alpha snapshots are completely
untested,
the situation can change from one day to another.
which is completely different situation than Firefox stable vs
Minefield. That's where your comparison lacks sense.
No, it's not. The situation is and was: *Untested snapshots* of any software.
It's not like KDE Network Management which during Factory development in
previous releases
got a single git snapshot and that was then stabilized for release. (Whereas
untested
snapshots of that are put in KDE:/Unstable)
Here the situation is that on a weekly basis untested snapshots are delivered
as regular
updates for openSUSE.
If there are any
issues with the latest release we should fix them and send to Google,
The Chromium package carries a large number of additional SUSE patches. I don't
see them
being sent to Google...
because I think if we had fixes against 15.x Google would not just care.Have you any evidence to back your thought up? Why would Google not want to
properly
maintain its current stable release?
If the beta branch (currently 16.x) was just mere days away from becoming the
stable
release, yes, I'd agree with you.
That said, if openSUSE at least moved to ship the beta versions, one could at
least argue
that it is already a stabilization branch and at least somewhat tested.
My main argument was and is openSUSE's release process and that it does not
permit
untested snapshots of any software to be included. So far nobody refuted that
argument --
neither here nor in the bug report.
I'm open to actual arguments and how and why the openSUSE's release process
would actually
prefer untested snapshots over release versions. So far I've only read 'You are
mean to
Raymond', 'I like Chromium', and 'The web moves fast'. So far no argument at
all about
openSUSE's release process policy.
Markus
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
To contact the owner, email: opensuse-project+owner@xxxxxxxxxxxx
| < Previous | Next > |