On Thu, Jan 12, 2012 at 1:01 PM, Christian Lohmaier <lohmaier+mag...@googlemail.com> wrote: > On Wed, Jan 11, 2012 at 10:09 PM, Juan Luis Baptiste <juan...@mageia.org> > wrote: >> [..] >> As I said, no one is talking about picking up a fix if there's a bug >> fix only release, it's for when it isn't and we need to reduce the >> chance of regressions by taking the modifications that *exactly* fix >> that bug. > > I strongly disagree. The policy is stating the exact opposite. And > also Michael seems to defend the policy as it is written, and not your > interpretation here. >
No, I'm doing exactly as the policy says, patch current stable version. The thing about bugfix only releases is something that it seems packagers have been doing implicitly as pterjan said before, and needs to be added to the policy. > That again you might have a different understanding of > bugfix-only-release. I think I stated mine often enough (increase in > micro version when package follows major.minor.micro versioning scheme > and no new features are introduced in micro releases). > This isn't always the case, some projects include both bug fixes and new minor features in a micro version bump release. So you have to check first the Changelog to be sure it only includes bug fixes (which I do not completely agree for some cases, but that's another topic). > So please change the wording of the update policy accordingly > https://wiki.mageia.org/en/Updates_policy reads: > ########## [...] > ########## > I read it as "no version bumb is allowed (except for the three > exception-cases listed) - bugs are only fixed using patches", and I > don't see the interpretational freedom to allow upstream's bugfix > releases. Updating from 1.3.2 to 1.3.3 would not be in compliance with > the policy (if not in one of the three exception cases) - this is what > I have called stupid policy (and still do). > Yes, this must be added to the policy to avoid more confusions. -- Juancho
