[Mageia-dev] How will be the realese cycle?
bgmilne at multilinks.com
Mon Oct 4 15:09:32 CEST 2010
On Saturday, 2 October 2010 09:34:23 Olivier Méjean wrote:
> Le samedi 2 octobre 2010 02:09:47, nicolas vigier a écrit :
> > This rolling release already exists, it's called the backport
> > repository. But don't expect the same stability as the fixed release,
> > you can't have both.
> Well, i disagree for a good reason, in free software there is no (or mainly
> no) separation between new versions of a software only correcting bugs, and
> new versions of the same software adding new functionnalities. Let's take
> an example, digikam.
> Changes from digikam 1.3 to 1.4 are bugs correction affecting digikam 1.3
> and addition of new functionnalities. So what ? I need digikam more stable
> so let's use the version that corrects bugs, so the latest, but it also
> adds new functionnalities that may provide bugs ... (and in the case of
> Digikam 1.4 it requires KDE 4.5, unfortunately there is no update to KDE
> 4.5 for Mandriva 2010 !) what to do ?
urpmi --searchmedia Backports digikam
If you have no regressions, use it, and report back to maintainer, or
contributor who backported it, and motivate for promotion to update.
If you have regressions, revert to version on main/release or main/updates,
report bugs upstream, await bugfixes from upstream.
Unless you're actually running 2010.0, in which case you seem to not support
your entire wish by your actions ....
> I also add that creating backports is creating new packages for older
> versions that is more time to compilation, more time to ensure quality,
> and so. In the whole i am not sure that it.
If you want rolling release, with all that brings (including sometimes,
untested packages, or packages that are not yet complete, but have to be
uploaded to allow completion of a difficult build dependency chain), run cooker.
If you want stable release with updated packages, request (or contribute!)
> So one cannot say that stability is affected by backport when backported
> packages are to correct existing bugs (but maybe adding new bugs due to new
> functionnalities). Noboby would say that KDE 4.1 is more stable than KDE
> 4.5 but there is no means to update KDE 4.x to KDE 4.x+1 at the moment,
> and i consider that must be in update policies. With Mandriva 2010 i am
> stick to 4.3.5 and i bet there will be no more evolution for KDE 4.3
Wait, you're complaining that software in the distribution is too old, but
you're running the previous release of the distribution (2010.0 I guess, but
you aren't clear).
More information about the Mageia-dev