On 12/10/2009 at 16:46, Vincent Untz <vuntz@opensuse.org> wrote: Hey,
So in case you don't want to work on factory stuff or you don't like cleaning BuildRequires/Requires, there's something else you can do!
We're planning to release GNOME 2.28.2 as a maintenance update for 11.2 (see the previous thread on this topic). While 2.28.2 is not out yet, we can still start updating quite a few package from 2.28.1 in GNOME:STABLE:2.28.
You can get a first list with: osc collab --project GNOME:STABLE:2.28 todo (install the osc-plugin-collab from openSUSE:Tools if you don't have it already)
Most of those updates should be easy to handle. It is really important to make sure to list the changes from upstream (which are usually listed in the NEWS file), so that we can review the changes and decide this new version is suitable for the maintenance update. You can just look at how previous .changes entries are formatted to get an idea on how to do it.
Oh, and if you don't know osc collab, this line will do most of the magic for you: osc collab --project GNOME:STABLE:2.28 update $package (where $package can be gnome-keyring, for example)
People in #opensuse-gnome will be glad to get you started, I'm sure :-)
I think the process is all fine, but I would prefer that the final SR goes against a staging repo (Maybe GNOME:UNSTABLE:2.28.2 or so?). We do have users that have the G:S:2.28 repo enabled in their system and offering 'half a 2.28.2' might not be the desired effect, as testing it at any moment just can't be done. And using the real end user as our test candidates (non-voluntary) is not a nice thing to do. Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org