RPM submission procedure

[Enrico Scholz]

ronny-vlug at vlugnet.org (Ronny Buchmann) writes:

>> No, when a package is in a public repository it is too late. People will
>> begin to use this repository as default one since it has lots of cool
>> packages. Since packages are already published, bugreports will have a
>> low priority for the packagers and bugs stay forever (rawhide is a good
>> example).
> I don't think this is a problem. When rawhide bugs are not maintained this 
> mostly means they are gone

A basic package like 'procps' is broken for nearly two months already...


> or they didn't really exist or the reporter has no real interest in
> it.

What can a reporter do? Shall he setup a cronjob which enters "problem
still exists" comments regularly?

But it is true; when a bug is ignored in rawhide for a certain time I
begin to use workarounds and can not answer later questions since
reproducing the problem would lead to painful reconfigurations.


> None would be a reason not to publish the package for testing.

'testing' in fedora.us terminology means: "I am not sure if it is
stable or unstable". Coming back to 'procps': this package is neither
stable nor unstable, just unusable and should never have entered a
public repository.

I remember other packages like sudo or vixie-cron which were given in
the same, non-functional state into rawhide.

Therefore it is important that there is a QA which tests packages before
they will be published at a public place.


> Testing is not for the faint of heart. Why should Fedora Extras
> testing be more stable than Fedora Core testing (aka Rawhide)?!

Because packages will stay there forever (like in the current fedora.us
QA queue) and people will begin to use this repository by default.  And
rawhide like repositories are nothing for Joe User...



Enrico

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=110263