Re: Proper Release Notes for 4.11?

Markus <[email protected]>
Newsgroups gmane.comp.kde.events
Message-ID <3844566.RUzM1kojtI__41413.3910010152$1372592768$gmane$org@schlepptopp.site>
So, there seems to be no interest in a proper Release Notes document. Too bad 
you guys don't my free contributions...

Am Mittwoch, 19. Juni 2013, 15:32:23 schrieb Markus:
> Here for the promo list as well after it was suggested to me top involve you
> as well:
> 
> Am Montag, 17. Juni 2013, 17:21:56 schrieb Markus:
> > Hello.
> > 
> > Yesterday I installed 4.11b1 and noticed a few things that should be
> > communicated to the public but are outside the scope of a normal release
> > announcement.
> > 
> > I think a proper Release Notes document would be wise detailing these
> > aspects. The most drastic change I find noteworthy is the improved Nepomuk
> > architecture. Because of it the DB first is automatically optimized and
> > then large parts need to be re-indexed (eg. apparently all mails).
> > This is not a bug but it could lead to confusion and possibly frustration
> > if not properly communicated because that process eats CPU power for a
> > while.
> > 
> > I'd like to contribute to a Release Notes document.
> > Is any already been planned or should I create one in the Community Wiki?
> > 
> > Markus
> > 
> > _______________________________________________
> > Kde-testing mailing list
> > [email protected]
> > https://mail.kde.org/mailman/listinfo/kde-testing
> 
> _______________________________________________
> 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.