On Wed, May 16, 2012 at 12:41 PM, Myriam Schweingruber <myr...@kde.org> wrote:
> Hi everyone,
>
> after checking with Aaron and to make bug handling easier I have set
> versions and milestones to the product "plasma" in
> http://bugs.kde.org.
>
> It would be great if you could from now on use the commit hook
> FIXED-IN when you fix a bug. The currently available milestones you
> can use are:
>
> 4.6
> 4.7
> 4.8
> 4.8.1
> 4.8.2
> 4.8.3
> 4.8.4
> 4.9-git
> 4.9.0
> 4.9.1
> 4.9.2
>
> The milestones prior to 4.9.0 can be used by triagers when finding
> fixed bugs that were not closed already.
>
> A default milestone can be set as a target if there is need for, I
> left it blank for now.
>
> I didn't add product versions prior to 4.5 as this is already obsolete
> anyway, so all reports for 4.5 or before have exactly that version
> number: "4.5 or before".
>
> Please tell me if a version is missing or something needs to be changed.
>
> Regards, Myriam
> --
> Proud member of the Amarok and KDE Community
> Protect your freedom and join the Fellowship of FSFE:
> http://www.fsfe.org
> Please don't send me proprietary file formats,
> use ISO standard ODF instead (ISO/IEC 26300)
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
I'm sorry but I never understood the FIXED-IN: tag, if somebody
explains it maybe if I understand it, it will be easier to add this
information (like I've done with others, like BUG).
In git you know if a bug it's fixed in a release because the release
log contains the bug fix. That is:
git log KDE/4.8..KDE/4.9 | grep "BUG: <id>"
To know if it's in a minor version, we can check if it's after the
release tag (if it's after 4.9.2 tag, then it's in 4.9.3).
So, what does FIXED-IN tag offer? Or is it just a hack because we
don't have the proper tool set?
Aleix
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
