Alexey Eremenko wrote:
Maintainer's tasks
1. * The package should follow the SUSE Package Conventions, it has to build on both ix86 and x86_64 and you should test it at least on ix86 (??? OK if the maintainer has no x86_64 machine for testing?).
I think packages need to be tested on either x86 or x86-64, not both. For kernel packages, we need to test on both architectures.
I changed it to: "... you should test it at least on one of the architectures. During the alpha and early beta phase of Factory, it is OK if you test the package on the latest openSUSE release only, but you should install a beta at some point of time and test your Contrib packages there."
2. # # (??? Add the package to a staging repository first? See http://lists.opensuse.org/opensuse-factory/2008-08/msg00264.html)
What do you mean ? "contrib-devel" repo ? Ahh I see - it is more like "temp". I don't see any advantage of that versus User OBS, but I may be wrong. Opinions.
Pascal? Are you subscribed?
1. # # If the package is actively maintained upstream (??? Relax this rule for packages with little or no security risks, like games without multiplayer mode?)
Yes, I think we can relax this rule for non-network packages.
It now reads "If the package is actively maintained upstream. Exception to this rule are packages with little or no security risk, but the package maintainer should be able to keep the package working in openSUSE in such cases." Michal -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org