Unhelpful update descriptions

Dan Mashal dan.mashal at gmail.com
Tue Mar 12 02:29:39 UTC 2013


On Mon, Mar 11, 2013 at 7:27 PM, Mathieu Bridon
<bochecha at fedoraproject.org> wrote:
> On Mon, 2013-03-11 at 12:06 -0400, Jared K. Smith wrote:
>> On Mon, Mar 11, 2013 at 11:41 AM, Michael Catanzaro
>> <mike.catanzaro at gmail.com> wrote:
>> > Perhaps the update policy should have a guideline on the minimum amount
>> > of information required in this description. E.g. "update to latest
>> > upstream version" might be a perfectly acceptable description for Fedora
>> > given the fast pace of updates, but I don't think users should ever be
>> > seeing "no update information available" and especially not "here is
>> > where you give an explanation of your update." (And I've seen this one
>> > multiple times within the past couple of weeks.)
>>
>> I tend to agree here.  That being said, most of my package updates are
>> something along the lines of "Update to upstream 2.5 release" -- would
>> you find that descriptive enough, or still lacking in detail?
>
> Perhaps add a link tot he upstream changelog, provided it is accessible
> on the web? (e.g a wiki page, in their VCS viewer, etc...)
>
>
> --
> Mathieu
>
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel

For what though?

You can google it and find it too. And on minor release versions they
sometimes don't update the ChangeLog at all until the major release
version.

You're better off watching github commit history half the time.

Dan


More information about the devel mailing list