![](https://seccdn.libravatar.org/avatar/036efc5132b2df24eac525839eef1038.jpg?s=120&d=mm&r=g)
On Freitag 30 Januar 2009 12:40:00 Henne Vogelsang wrote:
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.
ok: In this case, you lost at least me as packager for contrib.
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.
What about security issues with CRD? They shouldn't be visible in public... ...so: Can the current Novell Security Team handle security issues in Contrib via Bugzilla?
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?
I'm just thinking about people currently using the official openSUSE Update-Test repositories. They want is easy to test whatever will be released in the next update cycle. If you say: "Each package maintainer has to find his own way to get testers for his package outside the Contrib repository", you make it harder for people to participate.
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 :)
Well, for Education we're currently NOT using the buildservice for our frozen repositories. We use the Buildservice for development and preparing package updates... So we have at least 3 different repositories: 1) Development repository => OBS:Education 2) Frozen repository => repo/1.0/11.1 for example 3) Update repository => updates/1.0/11.1 for example Might be an idea to setup a similar setup for contrib? CU, Lars -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org