Re: 4.9 release notes

Carl Symons <[email protected]>
Newsgroups gmane.comp.kde.events
Message-ID <CAPu7pzJFrzOOss0NAPt+z8zQc_hfm8OAdj2EZBZczUhL95nkAA__4196.42993151701$1342717384$gmane$org@mail.gmail.com>
On Thu, Jul 19, 2012 at 4:17 AM, Albert Astals Cid <[email protected]> wrote:
> --- El jue, 19/7/12, Frederik Gladhorn <[email protected]> escribió:
>
>> Torsdag 19. juli 2012 13.03.21 skrev Sebastian Kügler:
>> > Hi all,
>> >
>> > Just a quick reminder: 4.9.0 is at the door, and we
>> need release notes for
>> > that. I won't be able to work on that as I'll be
>> travelling until one day
>> > before the release, but I also haven't seen any work on
>> that (might have
>> > missed it).
>>
>> Quick reminder: we'll change the release notes to be a
>> "normal" news.kde.org
>> article. The reason is that this avoids duplication (having
>> a stub on
>> news.kde.org linking to the announcement page) and thus
>> makes the site more
>> manageable for the web team. It also means that it doesn't
>> show up twice on
>> kde.org (as news rss and the actual article). This will be
>> the first
>> announcement in the new style.
>>
>> This means you'll get the dot editors as backup in getting
>> the announcement
>> out. :)
>
> Not sure i understand what you mean, do you mean that there won't be no announcement at all (or just a link) in www.kde.org and all the actual content will be in news.kde.org?

Yes, there will be an announcement.

In the past, the main announcement has been made on
http://kde.org/announcements/ with a synopsis on the Dot pointing to
that announcement.

Frederik and Ingo suggested that this was unnecessary, that a single
Dot story would be just as effective, and that this structure would
make things easier for website administration.

dot.kde.org and news.kde.org point to the same content.

>
> Are you aware that severely limits the possibility of translating the announcement?

No, I'm not. How are translations done now? What needs to happen to
keep translations viable?

>
> I'm not going to fight against that, but if that is the decision, whoever made that decision should communicate it to our translator teams.
>
> Cheers,
>   Albert
>

It was a suggestion to the specific players who have been involved in
release announcements previously. It is now communicated. What do we
need to do for this to work? The past 2 announcements have not had
much in the way of translations (4.8 Persian; 4.7 Estonian, Russian,
Ukrainian)

Content is needed. Sebastian has pulled this together in the past. Who
from the Release Team is doing it in his absence? Content includes
release highlights (usually one general announcement and one for each
piece - Platform, Applications, Workspace), screenshots, links.

Screenshot guidelines needed...
In the past, someone provided guidelines for screenshots (screen size,
resolution, font, default wallpaper) so that they would be consistent.
Would someone please provide these? What is the default wallpaper for
4.9 Desktop?

We collaborate in an etherpad at promo.notes.kde.org. Anybody who will
be working on the announcement needs to have access there...please
tell me if you need this.

Carl



>>
>> Greetings
>> Frederik
>>
>> >
>> > Is anybody planning to work on the release notes?
>> >
>> > Cheers,
>>
>> _______________________________________________
>> This message is from the kde-promo mailing list.
>>
>> Visit https://mail.kde.org/mailman/listinfo/kde-promo to
>> unsubscribe, set digest on or temporarily stop your
>> subscription.
>>
>
> _______________________________________________
> This message is from the kde-promo mailing list.
>
> Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.

_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.