[Mageia-dev] [changelog] [RPM] cauldron core/release pango-1.32.0-2.mga3

[Jani Välimaa]

2012/9/28 Shlomi Fish <shlomif at shlomifish.org>:
> Hello Jani,
>
> On Fri, 28 Sep 2012 11:37:36 +0300
> Jani Välimaa <jani.valimaa at gmail.com> wrote:
>
>> 2012/9/27 shlomif <buildsystem-daemon at mageia.org>:
>> > Name        : pango                        Relocations: (not
>> > relocatable) Version     : 1.32.0
>> > Vendor: Mageia.Org Release     : 2.mga3
>> > Build Date: Thu Sep 27 22:04:25 2012 Install Date: (not
>> > installed)               Build Host: jonund.mageia.org
>> > Group       : System/Internationalization   Source RPM: (none)
>> > Size        : 1062810                          License: LGPLv2+
>> > Signature   : (none) Packager    : shlomif <shlomif>
>> > URL         : http://www.pango.org/
>> > Summary     : System for layout and rendering of internationalized
>> > text Description :
>> > A library to handle Unicode strings as well as complex bidirectional
>> > or context dependent shaped strings.
>> > It is the next step on Gtk+ internationalization.
>> >
>> > shlomif <shlomif> 1.32.0-2.mga3:
>> > + Revision: 298828
>> > - New release - mkrel 2 - bug fix for crashes.
>> >   https://bugzilla.gnome.org/show_bug.cgi?id=684959 .
>>
>> IMHO new release is pretty obvious and there's no need to mention it
>> in changelog entry.
>
> Actually, there is. This way one can find where the release was changed
> based on "svn log -v", and temporarily revert the working copy to previous
> versions. This is because, unfortunately, there's no way to see the patches to
> the working copy in the logs.

To see when the release was changed we have "Revision: XXXXX" in
%changelog. You can also use 'mgarepo rpmlog <pkg>' to get the pkg
changelog from cmd or use svnweb.mageia.org to see the changes more
closely.

>
>> I don't have strong opinion about URLs in
>> changelog, but something fights against them. Haven't checked if
>> they're useless (does rpmdrake support clicking them?).
>
> You can always copy and paste them.
>
>>
>> IMHO much better  %changelog entry would have been:
>>
>> - add a patch from upstream to fix crashes (bgo#684959)
>
> What the hell is "bgo"? We should be more helpful and explicit than that. See:
>

An abbreviation for Bugzilla.Gnome.Org, widely used by other distros
(mdv/suse/fedora/etcetc) too in their %changelogs. Just like for an
example are rhbz (redhat bugzilla) and fdo (freedesktop.org) used.

IIRC there is a policy (maybe just a draft) where's mentioned that
when referring to external bugs the format should be "(XXXX#12345)"
where XXXX stands for some abbreviation like bgo and numbers stands
for the bug number.

> http://blog.trustedadvisortoolkit.com/what-do-you-mean-by-wdym/
>
> Regards,
>
>         Shlomi Fish
>