Re: 4.6 Releases Need You!

Stuart Jarvis <[email protected]>
Newsgroups gmane.comp.kde.events
Message-ID <[email protected]>
On Mon, Jan 17, 2011 at 8:24 PM, Stuart Jarvis <[email protected]> wrote:
> On Monday 17 January 2011 10:41:34 Sebastian Kügler wrote:
>> Hey,
>>
>> On Sunday, January 16, 2011 13:42:25 Stuart Jarvis wrote:
>> > I just spent a bit of time on the 4.6 release announcements...
>> >
>> > So questions:
>> > - Sebas - can you deal with all the html formatting or should we do that
>> > in  the shared doc?
>>
>> I can deal with that, having the texts good quality, it becomes manageable.
>
> Cool :-) We'll try and make some good quality texts then...

I've spent some more time. This still *really* needs wider review to
make it good.

>> > - Sebas (again...) - the discussions at Akademy concluded that we should
>> > not  have an SC announcement and only the 3 announcements: workspaces,
>> > apps and platform. Is this practical from the www infrastructure pov
>> > right now - can we have three announcements linked directly from the www
>> > front page? Or do we need a little SC announcement somewhere that just
>> > points to the others? (as per 4.5)
>>
>> It's something that's in our hands, one umbrella announcement makes it
>> easier to do within our current process/setup, but we should be able to
>> squeeze in three, too.
>>
>> We'll need a short SC blurb anyway, since we cannot send out three warnings
>> to the press channel, and then again three announcements. People would
>> (rightfully) hate us for spamming.
>
> Ok, so we'll prep an SC announcement too. We can see if it looks ok to have
> three announcements on the main www site, if not go with the short one.

Added to the top of the etherpad doc. This can also form the basis of
a dot article - in fact this can be more or less copy pasted if it
comes to it and then linkified to the annoucement

>> > - Anyone running 4.6 pre-releases - We need screenshots. If you don't
>> > have somewhere else to store them, you can use the promo wiki for
>> > upload. Or mail  them to me an I can host them. Please add links in the
>> > announcement texts.
>>
>> For screenshots, please keep in mind the following:
>>
>> - use the standard wallpaper (Horos)
>> - use Oxygen as widget set
>> - use default colors
>> - use a sans-serif font, preferable Liberation point size 9
>>
>> Collecting screenshots from different sources is very difficult, and we end
>> up with a mess if we don't make them all as consistent as possible.
>
> Ok, well I'm updating my home desktop some recent SC4.6 pre-release, so if my
> system still works after that I should be able to make some screenshots

I've done what I can:
http://www.asinen.org/downloads/originals.tar.gz
http://www.asinen.org/downloads/cropped.tar.gz

(cropped are cropped according to my understanding and the guidance in
the promo wiki - originals are also there in case i screwed up so
someone else can have a go)

Italics in the etherpad doc reference possible locations for
screenshots and their captions - or where I couldn't make a screenshot
due to something breaking I've described what I think should be there.

Ok guys, I haven't got as much done as I wanted, but I'm now offline
(almost entirely, definitely no time to do more anyway) until the
morning of 26 Jan (maybe evening 25th).

That means that you're on your own, if the screenshots have some
hidden suck then you'll have to try and create new ones - I won't have
access to a machine with 4.6 releases. Imho, the release annoucements
at the moment are not a disaster, but they can surely be made plenty
better :-)

Good luck!
Stu

PS - Nuno, the wallpaper is awesome :-)
 
_______________________________________________
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.