[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2

[Maarten Vanraes]

Op donderdag 15 december 2011 21:18:44 schreef Juan Luis Baptiste:
> On Thu, Dec 15, 2011 at 2:51 PM, Florian Hubold <doktor5000 at arcor.de> wrote:
> > Huh? From what i remember the only difference between backports
> > and updates should be that backports are mostly new versions,
> > new features, but the QA should be the same. If that's not the case,
> > seems my memory from the last few meetings played tricks on me.

iirc in some meetings there was some discussion on QA availability with 
security updates not being fixed fast enough, or something and that backports 
still should contain testing, but not as much as updates, due to lack of 
manpower and such.

of course, there's been alot of meetings on backports(and less results), so i 
can't really be sure of the accuracy of this last paragraph...

> Well we're going off the track of the meaning of this thread but my
> opinion on this: I agree with Marteen, it would be unrealistic on
> thinking on putting the same amount of work of QA on backports than in
> updates. How would be the way to go ? get a list of the new features
> of a program and have a QA member test each one of them ?? I don't
> think that's a good idea, it would take a lot of time and the person
> testing should know fairly enough how the program in question works.
> In that case the same QA should be put each time a new version of a
> program is updated in cauldron, and that also is not possible to do.
> 
> I think in the case of backports tests should be much more lax than in
> updates: it installs runs and if there's any important bugfix
> mentioned in the changelog make sure that it is fixed, there's no
> other way around it. If not then do not have backports at all and let
> third party repos continue to pop up to fulfill this need.

don't get me wrong, my position isn't as such that there should be less QA in 
backports than in updates, but that there should be more QA in updates than 
there is with backports.

as i mentioned before, the important difference in updates and backports, is 
the new features, as such backports are new versions of software, while 
updates are the _same_ version and should do everything (except the bug) the 
same.

lastly, doktor5000: you say this is no everyday update... and i agree with 
that. it's exactly that reason that should make this backport and not update. 
(except also for our current policy on new features).

AL13N