[Mageia-dev] Backports policy proposal

Buchan Milne bgmilne at staff.telkomsa.net
Fri Jun 24 16:19:45 CEST 2011


On Friday, 24 June 2011 08:30:15 Maarten Vanraes wrote:
> Op vrijdag 24 juni 2011 02:10:14 schreef Michael Scherer:
> [...]
> 
> > Another rule that we could add is that cauldron should always be newer
> > than backports, in order to ensure upgradability. The same goes for n-2
> > and n-1 release.
> > While this seems innocent, do not forget this will have a impact when we
> > do the version freeze.
> 
> [..]
> 
> This seems hard to enforce... i can imagine if you make backport, it has
> essentially the same version as in cauldron, i can think that there is a
> few spec file changes that are only for backports,

Why should it need spec file changes?

> and thus the release
> becomes newer than the one in cauldron

If it requires spec file changes, why should cauldron not get a new release 
that includes the changes?

Sorry, but a number of my packages were regularly backported, and I never 
needed cooker to be older ...

Regards,
Buchan


More information about the Mageia-dev mailing list