Sorry for my late answer, but i could not read it before. > If one does another update (i.e. adds subrel), it should mean that the > fixes/whatever have been done to the cauldron tree first and thus > cauldron has 1.0-2.mga1, while mga1 gets 1.0-1.1.mga1. That's also my point of view... Maintainer or who fixes the package must bump release in cauldron in such a case and if it is a fix that fixing should be ported in cauldron as well.
As said by coling in a mail after, sometimes a package that is backported
needs to be patched to build in stable, but in that case i can't see
why we need to add subrel... let's leave the same version.
After that any following release falls in the previous case e.g. bumping
cauldron.
A rebuilding for any reason in stable *must* be followed by a release bumping
in cauldron if there's no package release changes there.
Another thing, i agree we have to move up, but the chosen (i seem it's been
decided already) policy requires more work for packagers, so we complain we
have few packagers, and do we overload them?
I believe we could add a robot who catches a package that is higher in stable
than in cauldron, we already check it for upstream/other distro version...
A package that falls in that case can be considered as all the other in
broken dependency....
WDYT?
--
Angelo
signature.asc
Description: This is a digitally signed message part.
