On Mittwoch 23 November 2011 19:10:46 Raymond Wooninck wrote:
Unfortunately a bug report was created (bnc#731832)
Why unfortunately? Shipping the alpha versions in openSUSE-current (not Factory) is a bug. I reported the bug through the proper channel.
So officially there are no alpha, beta or stable versions of Chromium Nonetheless Google releases three Chromium versions more or less simultaneously. That's because one is an alpha snapshot, one is the beta for the upcoming stable version, and one is the current stable version.
Claiming that Chromium development is completely disconnected from the release schedule of Google Chrome is just as disconnected from reality. New Chromium versions are released together with new Chrome versions. They are the same with the exception of a handful of Google features in Chrome. So when Google declares 17.x alpha, 16.x beta, and 15.x stable then that's also the same for Chromium.
and it is up to each dsitribution to decide what they want to ship. For openSUSE 12.1 it is too late to change anything here as that this would mean that existing users might experience loss-of-data as that their profiles are not compatible with lower versions of Chromium.
Not exactly true. For 12.1 you could continue to ship 17.x versions until 18.0 reaches stable status. The real question is: What are Current and Factory for? My impression is that Factory is for reasonably tested software and Current for fully tested software. Your weekly snapshots are just that: Snapshots. They are untested and not even from a stabilization branch. That said, you can obviously package what you want. If you prefer untested alpha snapshots then so be it. However, untested alpha snapshots do neither belong in openSUSE-current, nor Factory. Your Chromium snapshots would need to be treated like Firefox betas are treated, ie. put in a separate repository. Markus -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org