On Wed, 20 Jun 2001, Vincent Danen wrote:
> > > > How many more times should I report this bug? :-(
> > > Exactly when did you report the bug? Is it possible the packages were
> > > built prior to your reporting the bug? Did you check the cooker
> > > packages?
> > > rpm -qip the kdelibs packages and see if it was built after you
> > > reported it.
> > Reported Jun 10, at which time 2.1.2-3mdk was not available on any of the
> > mirrors that I check (both rpmfind and proxad.net). The problem therefore
> > seems to be in the mirroring: both rpmfind and proxad are (AFAIR) primary
> > mirrors and so I usually treat them as being definitive; if a package is
> > not present then I assume it doesn't exist.
> QA process is not a 24hr deal... =) It sometimes takes a little bit
> longer, and kdelibs is a big package that needs thorough testing
> (this isn't cooker we're talking about!). So the delay is not in
> mirroring, but in QA. We could do it faster and not as thorough, but
> then we'd be doing it over again many more times, I'm sure.
OK, that makes sense, but how about releasing the packages to cooker as
soon as they are built and then releasing as updates once QA is complete?
That way, everyone knows when an update is being worked on and you also
benefit from extra testing.
Just a thought,
Michael
