Hi, on 01/30/2009 02:11 AM Lars Vogdt wrote:
1) How frozen is frozen?
As far as I understand, contrib will contain Contrib:Factory => current development Contrib:<release> => frozen repository
Correct.
Each maintainer should maintain his package for Contrib:Factory and Contrib:<release>, right?
Yes.
As contrib:<release> is frozen (cite: "After the branch no version updates are allowed anymore") - is there really no chance to upgrade a package?
We are mimicking Factory. So the same rules apply.
2) What about orphaned/unfixed packages? If a package fails in contrib:factory or needs a security fix in the contrib:<release> repos - what's the expected response time?
ASAP :)
Who escalates/detects, if a packager is not responding?
I'm sure the security team will notify this list. We did not talk about this yet.
3) Is there a jury and/or escalation method defined to settle potential disputes between contrib-reviewers and contrib-maintainers (updates/reachability) ?
In general: Reviewers win. Everything else has to be decided on a case by case basis.
4) How to test updates?
If a packager has to fix a package for a frozen distribution and wants some people to test it - how should this work? * Would there be a Contrib:<release>:testing repository for this? * Should testers add the packagers home repository (containing perhaps other packages) and install from there?
Up to the Maintainer and his testers. Why do you think should we "regulate" this?
5) How will users be informed about updated packages for their release?
We talked about this briefly if we need security announcements for Contrib. We did not come to a conclusion yet.
Is it perhaps possible to get a "real update repository" containing patchinfos (the files which can be shown in the updater-applet on my desktop) for released contrib repositories (like Education does ;-)?
Of course we can do this. In general: As you can see we have not put too much thought into the release of Contrib yet. You are welcome to drive this as you obviously have experience with this in Education :) Henne -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org