bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: reduce the news in home page


From: Urs Liska
Subject: Re: reduce the news in home page
Date: Mon, 16 May 2016 16:20:26 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0


Am 16.05.2016 um 18:12 schrieb Federico Bruni:
> Il giorno lun 16 mag 2016 alle 9:34, Urs Liska <address@hidden> ha
> scritto:
>> However, I suggest that once this is completed we reconsider the
>> old-news display.
>> Currently there's http://lilypond.org/old-news.html where all old news
>> and release announcements are mixed. As noone will usually browse
>> release announcements that essentially means that old "real" news items
>> are effectively buried.
>>
>> May be the release announcements should directly be moved to
>> http://lilypond.org/attic.html so we have the old news page less
>> cluttered as well?
>
> I agree: release news should be separate from other news.
>
> Most of release news are just noise (same copy&paste). Not only for
> readers, also for translators. I never translated news into italian
> because of this.. and I'm in good company:
>
> $ find Documentation/ -name news*.itexi
> Documentation/zh/web/news-front.itexi
> Documentation/ca/web/news-front.itexi
> Documentation/es/web/news.itexi
> Documentation/es/web/news-front.itexi
>
> Turning all those release news into something a bit more useful (other
> than the release date) would be nice, at least for the next ones.

Or maybe not keep them at all. Instead keeping one list with the release
dates of all previous versions, maybe with a link somewhere?

>
> What about linking to the list of commit messages for a certain
> release in gitweb?
> http://fazigu.org/blog/2011/03/31/gitweb-diffs-between-versions/
>
> The following link should show the commit messages included in 2.19.41
> release:
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=log;hp=f650af5;h=87aa275
>

Might be a good idea, but *only* as a strictly additional information,
something like: For all those who want to know in detail what's in that
release ...
Such a display won't make much sense for the common user who doesn't
even know what a Git commit is.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]