Re: Plasma 5.8 LTS
Torsdag den 14. juli 2016 01:05:51 skrev Albert Astals Cid: > El dilluns, 11 de juliol de 2016, a les 8:37:12 CEST, Jonathan Riddell va > > escriure: > > On Mon, Jul 11, 2016 at 09:30:59AM +0100, Jonathan Riddell wrote: > > > Incase anyone missed it, we have had a kickoff meeting for Plasma 5.8 > > > and decided to make it an LTS release with updates continuing for 18 > > > months after release and depending on Qt 5.6 (also LTS). Release is > > > mid-October. > > > > > > http://jriddell.org/2016/07/08/plasma-5-8-lts-kickerd-off-for-stability-> > > > > > an > > > d-performance/ > > > > Having decided that, we need to work out the faffy stuff to make it > > possible. It presumably needs a new branch for i18n for the LTS and > > possibly a new pointer to the LTS branch in repo-metadata. Who should I > > talk to about making those happen? > > We historically only support only one stable branch in KDE i18n. > > I don't see myself adapting all our scripts and websites to support another > additional stable branch. > > Since it's going to be a "stable" branch and won't have new strings do we > really need a new branch for it? Speaking as a translator I agree with Albert that it's probably not worth the effort creating another l10n branch. Translators will have 4-5 months to complete 5.8 translations before 5.9 enters the stable branch. And after that point very few translators would pay attention to the 5.8 branch anyway, since it would require some additional workflow, new Lokalize profiles etc., for very few string changes, if any at all. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: String Freeze Exception in Baloo
Mandag den 28. juli 2014 16:16:28 skrev Vishesh Handa: > We introduced a new query parser module in Baloo for 4.14. This module used > '%1' as a placeholder in many of the strings. This '%1' was just a > placeholder. Unfortunately, KLocalizedString when compiled in release mode > would replace this %1 with K18N_ARGUMENT_MISSING, making the module useless. > > If it's alright with you guys, I would like to stop using %1 in our strings > and now use $ instead. See - https://git.reviewboard.kde.org/r/119519/ > > This would unfortunately break many of the existing translations. Possible > options - > > 1. Break the translations. This module isn't publicly used anywhere. > Doesn't matter. > 2. Do not ship the module for 4.14. It's not used anywhere, so we can do > that. > > I would prefer doing (1). If there are no objections I'll commit the patch. OK from DA But I suppose you accidentally sent this message to the release team list instead of kde-i18n-doc by mistake? ;-) ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Virtuoso 6.1.5 is buggy
Tirsdag den 17. juli 2012 20:38:25 Vishesh Handa skrev: > Please avoid using Virtuoso 6.1.5 with Nepomuk from kde 4.9. Does that imply virtuoso 6.1.5 + KDE SC 4.8.x is a safe combo? ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Time to Dump kdewebdev and kdetoys?
Lørdag den 19. maj 2012 10:17:18 Burkhard Lück skrev: > Am Freitag, 18. Mai 2012, 22:06:19 schrieb Allen Winter: > > kdewebdev has had zero love and attention for a long time now. > > Wrong, kfilereplace, kimagemapeditor, klinkstatus have an up to date > documentation since 4.7, see > http://techbase.kde.org/Projects/Documentation/KDE4_(health_table)#kdewebdev Speaking from a user perspective. I use kfilereplace and klinkstatus, and they work fine. Don't see any reason to dump them unless there'd be security issues. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.6.0: go or no go?
Tirsdag den 18. januar 2011 20:56:00 skrev Frank Reininghaus: > Am Dienstag 18 Januar 2011, 20:06:52 schrieb Aaron J. Seigo: > > On Tuesday, January 18, 2011, Frank Reininghaus wrote: > > > Am Dienstag 18 Januar 2011, 17:57:01 schrieb Aaron J. Seigo: > > > > > There is a bug which lets some KDE apps (especially Dolphin) crash > > > > > every time they are closed: > > > > > > > > > > https://bugs.kde.org/show_bug.cgi?id=257944 > > > > > > > > has strigi devels been contacted / drawn into this? > > > > > > all the Strigi web content I found looks quite outdated, but if anyone > > > knows how to contact people who work actively on Strigi, drawing their > > > attention to the bug report would certainly be a good idea. > > > > Jos van den Oever is still "at the helm" afaik and the mailing list is > > still active, if low volume, at strigi-de...@lists.sf.net .. > > thanks, I sent a mail to that list asking the Strigi devs to have a look at > the report. The openSUSE problem seems to be fixed by updating to strigi "0.7.3.99". Not sure if the problem with strigi 0.7.3 was an upstream bug or a packaging issue on the openSUSE side or something else. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [Kde-pim] KDEPIM Needs More TIme
Torsdag den 20. maj 2010 16:26:15 skrev Allen Winter: > On Thursday 20 May 2010 9:30:51 am Eike Hein wrote: > > On 05/20/2010 11:36 AM, Dirk Mueller wrote: > > > so kdepim should be excluded from 4.5 tagging. what about kdepimlibs? > > > > > > will kdepimlibs 4.5 work with kdepim 4.4? has this been tested? > > > > There was a discussion about this in #kde-devel yesterday > > where tmcguire reaffirmed that this was the intended com- > > bination and said they had people running it as well. > > Yep. Will the offsetting of kdepim by one month from the 4.5 schedule also include the message freezes? Or is kdepim now in soft message freeze like the rest of kde sc 4.5? I am planning for 4.5 translation just now, and would like to know the implication of the kdepim plans for message freeze. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Release Coordinator
Tirsdag 09 september 2008 11:28:01 skrev Andreas Pakulat: > On 09.09.08 11:12:08, Martin Schlander wrote: > > I would be happy if you would add keeping this page reasonably up to > > date, to your list of duties: > > http://techbase.kde.org/Schedules/Extragear > > > > I know technically kdevelop isn't extragear, but.. > > You mean I should remove KDevelop from that page? KDevelop lives in > trunk/KDE not extragear. There's currently not even a place in extragear > where maintained releasable plugins could live, so I don't see why > KDevelop would be listed on that page. The point of the page is to have a somewhat centralised place where translators and others interested can keep track of upcoming releases without too much horsing around. Potentially it would also save release coordinators a little work regarding notifying kde-i18n-doc about releases and such I'd think. While KDevelop is not developed in extragear - it is in some sense "extra gear" for KDE. But if you think it's better to have techbase.kde.org/Schedules/KDevelop, or to not be listed under t.k.o/Schedules at all, that's of course up to you and your team. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Release Coordinator
Mandag 08 september 2008 23:05:49 skrev Andreas Pakulat: > I've checked the apropriate techbase page and just wanted to > double-check wethere there's anything, besides being subscribed to this > list and putting my name on the Release Team page on techbase, that I > need to do to "start" :) I would be happy if you would add keeping this page reasonably up to date, to your list of duties: http://techbase.kde.org/Schedules/Extragear I know technically kdevelop isn't extragear, but.. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
