Re: [RFC] Draft Roadmap for KDE 4.0
A Dissabte 03 Març 2007, Tom Albers va escriure: Hi all, I'm astonished, no comments for now, that can only mean that everyone agrees with you or that noone as a clue. Sebas pointed out that we need to setup a roadmap to the KDE4 release. As I think setting deadlines will actual help to reach goals, I've taken the time to setup a draft roadmap to KDE4. I've no experience in release schedules nor do I know the state of kdelibs or any other kde4 module, but I feel a draft document makes discussing things much easier. So here comes a draft schedule, lets work on the points and dates and publish it after that on the current Techbase page. kdelibs soft api freeze + alpha1 release - 2 April This is the the point where kdelibs api is frozen. That means that the classes and interfaces are not allowed to change anymore. That means the end of the famous bic Mondays. That's one month from now only, i'm not a libs developer, but it seems to few for me, true is that you leave the door open for changes, so maybe it's just me :-) If for one reason you feel the api should change, you need to post a kdelibs api exception request to kde-core-devel with the reason and the code. If there are no objections after a week, you can commit the changes, but all the kde main modules must compile and work as expected. kdelibs is also i18n frozen, exceptions can be asked on kde-i18n mailinglist. The release will not include translations. feature freeze- 2 may After this date the kde main modules are frozen for new features. No new features are allowed, the focus is from now on on stabilizing the applications and fix all bugs. This is also the date that all the maintainers of the main kde modules need to indicate if they will follow this schedule or will divert and will not be released together with kde 4.0. So have we really decided we want to go on with KDE 4.0 not beign a FULL release, that is, maybe not shipping kdepim? For me that'd be a loss, but maybe it's the best we can do, get 4.0 as fast as possible to start regaining steam. Albert message freeze- 2 June After this date the main modules are frozen for new messages. Exceptions can be asked on kde-i18n mailinglist. beta cycle starts - 2 Juli From this date on every month a beta version will be published, this will be repeated until most grave bugs are resolved. Translations are included from the second beta. kdelibs api is now frozen. release candidate cycle starts, total release freeze. - 2 September A RC will be released. If there is no grave bug in that release, kde 4.0 will be released, else new release candidates will be released every month. When the first release candidate there is a total release freeze active. This means that you can fix serious bug reports but nothing else. Before the first release candidate there will be a made of lists of languages which will be included in the KDE 4.0 release. This is based on the rules as usual. KDE 4.0 - 2 October Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: obsolete templates
A Dimarts 06 Març 2007, Stephan Kulow va escriure: Hi! Hi, thanks for attacking the i18n issue :-) I have a question and a comment. Question: Are playground modules beign parsed? okular has a Messages.sh but no template, are we doing something wrong? Commnent: messages/kdegraphics/kpdf.pot should be moved to messages/playground/graphics/okular.pot as most of the messages are the same or very similar. Albert I need your help. There are just too many obsolete templates for KDE4. Removed applications need to have their templates removed, renamed apps need to have their template renamed moved apps need to have their templates moved. Please help me out and tell me about things you know. Greetings, Stephan messages/kdeaccessibility/libKTTSD.pot messages/kdeaddons/kcmkuick.pot messages/kdeaddons/konqsidebar_delicious.pot messages/kdeaddons/konqsidebar_news.pot messages/kdeaddons/kuick_plugin.pot messages/kdeaddons/libkaddrbk_geo_xxport.pot messages/kdeaddons/libkaddrbk_gmx_xxport.pot messages/kdeaddons/rellinks.pot messages/kdebase/clockapplet.pot messages/kdebase/kdcop.pot messages/kdebase/kde-system-monitor.pot messages/kdebase/kio_mac.pot messages/kdebase/libdmctl.pot messages/kdebase/libkickermenu_tom.pot messages/kdebase/privacy.pot messages/kdeedu/keduca.pot messages/kdeedu/kturtle.pot messages/kdeedu/kverbos.pot messages/kdegames/ksmiletris.pot messages/kdegraphics/kcm_kviewcanvasconfig.pot messages/kdegraphics/kcm_kviewgeneralconfig.pot messages/kdegraphics/kcm_kviewpluginsconfig.pot messages/kdegraphics/kcm_kviewviewerpluginsconfig.pot messages/kdegraphics/kpdf.pot messages/kdegraphics/ksvgplugin.pot messages/kdegraphics/kviewbrowserplugin.pot messages/kdegraphics/kviewcanvas.pot messages/kdegraphics/kvieweffectsplugin.pot messages/kdegraphics/kview.pot messages/kdegraphics/kviewpresenterplugin.pot messages/kdegraphics/kview_scale.pot messages/kdegraphics/kviewscannerplugin.pot messages/kdegraphics/kviewshell.pot messages/kdegraphics/kviewviewer.pot messages/kdegraphics/libkfaximgage.pot messages/kdelibs/kioexec.pot messages/kdelibs/kmcop.pot messages/kdelibs/knotifytest.pot messages/kdelibs/ktexteditor_isearch.pot messages/kdemultimedia/artsbuilder.pot messages/kdemultimedia/artscontrol.pot messages/kdemultimedia/artsmodules.pot messages/kdemultimedia/krec.pot messages/kdemultimedia/noatun.pot messages/kdemultimedia/simpleplaylist.pot messages/kdenetwork/dcoprss.pot messages/kdenetwork/kcmktalkd.pot messages/kdenetwork/kcmwifi.pot messages/kdenetwork/kget.pot messages/kdenetwork/ksirc.pot messages/kdepim/kabcclient.pot messages/kdepim/kandy.pot messages/kdepim/kfile_palm.pot messages/kdepim/kgantt.pot messages/kdepim/kio_mobile.pot messages/kdepim/kmobile.pot messages/kdepim/kpilot.pot messages/kdepim/kres_exchange.pot messages/kdepim/ksync.pot messages/kdepim/libkpimexchange.pot messages/kdetoys/kodo.pot messages/kdeutils/kcmlaptop.pot messages/kdeutils/kedit.pot messages/kdevelop/kdevdesigner.pot messages/kdevelop/kdevelop.pot messages/kdevelop/kdevtipofday.pot messages/kdevelop/qeditor.pot messages/kdewebdev/kommander.pot messages/kdewebdev/quanta.pot messages/koffice/kscreenshot_plugin.pot messages/koffice/kspreadcalc_calc.pot messages/koffice/kthesaurus.pot messages/qt/kdeqt.pot ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
A Divendres 21 Setembre 2007, Stephan Kulow va escriure: Hi! It's been a while since KDE 3.5.7 (released may 22nd) and a lot has changed in the 3.5 branch since then, so I would like to release another service pack. As the translators requested some clean up time, I suggest we go with October 7th as tagging date and release on 15th. Any objections? If not, I let everyone know :) As a matter of saying i agree i created the changelog page up to r715588 http://www.kde.org/announcements/changelogs/changelog3_5_7to3_5_8.php Albert P.S: We should hide it in few time or pages will start linking to it saying 3.5.8 is out, though. Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Goals for the beta release.
A Diumenge 23 Setembre 2007, Tom Albers va escriure: Hi, As discussed in a thread last week, here is an overview of goals for the beta cycle: http://techbase.kde.org/Schedules/KDE4/4.0_Release_Beta_Goals As soon as all is green we can continue to the release candidate cycle. I will update the page as soon as I receive the info from the remaining projects. Toma In my opinion we should add having SSL/https support (Which thiago says we don't have at the moment) Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
A Dilluns 24 Setembre 2007, David Faure va escriure: On Sunday 23 September 2007, Albert Astals Cid wrote: A Divendres 21 Setembre 2007, Stephan Kulow va escriure: Hi! It's been a while since KDE 3.5.7 (released may 22nd) and a lot has changed in the 3.5 branch since then, so I would like to release another service pack. As the translators requested some clean up time, I suggest we go with October 7th as tagging date and release on 15th. Any objections? If not, I let everyone know :) As a matter of saying i agree i created the changelog page up to r715588 http://www.kde.org/announcements/changelogs/changelog3_5_7to3_5_8.php Nice! There's a bug with the core libs changes though. The first bugfix says See SVN commit 669594. and this is a link to http://websvn.kde.org/branches/KDE/3.5/kdelibs/core libs/?rev=669594view=rev which doesn't exist (see the core libs in there :) Too much automation in the xml-php transformation it seems? Yeah, it seems i tried to be too much smart, i'll fix it when i have time. Thanks for pointing out. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8 uploaded
A Dimarts 09 Octubre 2007, Andras Mantia va escriure: On Tuesday 09 October 2007, Albert Astals Cid wrote: It's the typical release procedure, we always protect pages until we do the real release. It is not typical for KDE. This is really the first time I see the changelog page protected in KDE (well, I'm not sure for 3.5.7, but before that for many releases I updated regularly the changelog files and it was never protected). I just protected yesterday, that is protect when the release is near. The files are read/writable for anybody having an account and readable for everybody else, so what is the real benefit of tryting to hide it, I don't know. I already explained, remove the confusion caused when smart sites link to the changelog and say kde has been removed. But as you say, they are read/write for anyone, feel free to remove the exit. What if somebody links there? They will see the progress of KDE, that's all. BTW http://websvn.kde.org/trunk/www/sites/www/announcements/announce-3.5.6.php?r1=626589r2=627062 http://websvn.kde.org/trunk/www/sites/www/announcements/announce-3.5.7.php?r1=667120r2=667267 http://websvn.kde.org/trunk/www/sites/www/announcements/changelogs/changelog3_5_6to3_5_7.php?r1=665435r2=667267 Albert Andras ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8 uploaded
I added a exit to the .php file because we don't want sites to start linking there before we do the actual release If you want to have a look at the changelog you can see http://www.tsdgeos.com/unofficial/changelog.html Albert --- Andras Mantia escribió: On Tuesday 09 October 2007, Stephan Kulow wrote: Albert was already so nice to create http://www.kde.org/announcements/changelogs/changelog3_5_7to3_5_8.php and we added kdevelop 3.5 to the mix, so there is something to announce. At this time the document is empty. It looks OK in the subversion repository though. Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Bringing ebn krazy back
Can we have it back already? Please? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Bringing ebn krazy back
A Dilluns 12 Novembre 2007, Matt Rogers va escriure: On Nov 11, 2007, at 1:40 PM, Albert Astals Cid wrote: Can we have it back already? Please? Albert Please justify why you need it. Because it's useful, that's a reason by itself, if you want particular examples I want to check i don't use any of the difficult to translate words (like Default, File, etc) without context. If you're running out of things to work on, there are plenty of bugs in trunk. :) Yes, but i first want to polish my apps before going to apps i don't use/know. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: beta5 or rc1
A Dilluns 12 Novembre 2007, Torsten Rahn va escriure: Albert Astals Cid wrote: okular still can't print (although it seems that might be done *soon*) so i agree Well at the current point of time there is no way to get heard if you won't get more specific and commit yourself on an exact point of time. Tell a reasonably estimated date when printing will be done (unless you get hit by a car) and chances are much higher that okular's showstoppers can get considered while planning the release. So are you able to tell whether printing will be ready by Wednesday 21st (just like plasma will have stuff ironed out by then) ? It seems likely to be working by then, yes, but it's not me doing the actual work, so i can not back it up 100%. Albert Torsten ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: String freeze ask
A Dimecres 21 Novembre 2007, Burkhard Lück va escriure: Am Dienstag 20 November 2007 23:48:53 schrieb Allen Winter: On Thursday 15 November 2007 03:33:23 Burkhard Lück wrote: Some other broken things regarding doctranslation: autogen.sh: autogen.sh?? l10n-kde4/scripts/autogen.sh, the script to generate the buildsystem files for the translated docucumentation. faq, glossary, quickstart, userguide, visualdict are installed in wrong dir and are therefore not visible in khelcenter those docs are installed in $KDEDIR/share/doc/HTML/en/khelpcenter. what is the correct install location? I can easily fix once I know where they should be installed. I mean the language docbooks, not the english docbooks. Attached a patch to install the language docbooks for faq, glossary, quickstart, userguide, visualdict in $KDEDIR/share/doc/HTML/language/khelpcenter. Seems ok language/common dir and the links in it are not installed $KDEDIR/share/doc/HTML/en/common exists so what symlinks do we need to create. please tell me what to do here. The directory $KDEDIR/share/doc/HTML/language/common is not installed. And in kde3 there are some symlinks in every language/common to some files in en/commen. I don't know if these symlinks are still needed for the kde4 language documentations. Probably they are needed too, but i'm not sure, so ignore me in this aspect :D Albert Burkhard Lück ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Application Version Numbers
A Divendres 23 Novembre 2007, Allen Winter va escriure: Note to all: We need to remind authors/maintainers to increase the version numbers on the applications before taggings. I nagged all kdegames maintainers, so you can write check there. Which brings up Dirk's (IIRC) idea of automatically assigning version numbers based on the KDE release number. I completely disagree in that scheme. Albert Anyhow... something for the pre-tagging To-do List... -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE Dev Platform Status
A Diumenge 25 Novembre 2007, Allen Winter va escriure: Howdy, Are we willing to permit BIC changes to the Dev Platform? The question you need to make yourself is: Did we release the 4.0.0 for the Dev Platform?, techbase says yes, so the answer to that question is no BIC changes until 5.0.0 Obviously you can ignore that we said to have released 4.0.0 for the Dev Platform and call it that was our 4.0.0 joke platform and then allow BIC changes. Albert If so, under what conditions? There are still requests coming into k-c-d for BIC changes to kdelibs and I'm sure there have been such changes since the hard freeze went into effect. For example, ossi's KCoreConfigSkeleton patch.. I'm inclined to allow this patch. ossi says it is safe and SC. and aseigo says he has a use case for it. I need some guidelines for allowing patches to the Dev Platform modules. -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE Dev Platform Status
A Diumenge 25 Novembre 2007, Allen Winter va escriure: On Saturday 24 November 2007 18:23:21 Albert Astals Cid wrote: A Diumenge 25 Novembre 2007, Allen Winter va escriure: Howdy, Are we willing to permit BIC changes to the Dev Platform? The question you need to make yourself is: Did we release the 4.0.0 for the Dev Platform?, techbase says yes, so the answer to that question is no BIC changes until 5.0.0 Obviously you can ignore that we said to have released 4.0.0 for the Dev Platform and call it that was our 4.0.0 joke platform and then allow BIC changes. Albert, Of course I agree, in theory. But we also need to acknowledge that we are not all-knowing super-geniuses with unlimited time and man+woman power. I don't think we need to be so hard on ourselves. I'm not beign hard, just realistic-pessimistic. I try to use KDE 4 everyday and i can't and i can't fix all things because i'm not a super-genius with unlimited time. So my suggestion is just to ignore we released kdelibs 4.0, make the BIC changes and release kdelibs 4.0.0 again. And besides i would want to suggest that KDE 4.0 should not be released on 11 december, but i won't do it and expect some crazy fixing goes along trunk and fixes everything for that date. Albert IMO we have a very short time window to implement critical BIC changes. And critical BIC changes that require no source code changes are even easier to approve. Anyway, that's my opinion. -Allen PS. moving libexec/kdesu to bin/kdesu would break the Dev Platform freeze. Do I continue with the co-installability stuff? ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Removing kregexpedit and kcalc
Both don't work at all, and there's no maintainer. I vote for them to be removed of KDE. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Removing kregexpedit and kcalc
A Diumenge 25 Novembre 2007, Richard Moore va escriure: Removing kcalc seems daft to me. It's pretty much essential for a sane desktop. Are you saying there are some problems with it that need fixing or just playing jobsworth? Problem i have: * I can't not start it, it ends up in an inifite loop Problem other people has: * It doesn't know how to add http://bugs.kde.org/show_bug.cgi?id=152713 Real problem: * No maintainer No playing here, i'm just not in mood. Albert Cheers Rich. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Removing kregexpedit and kcalc
A Dilluns 26 Novembre 2007, Richard Moore va escriure: I've just tested trunk and if I remove the kcalc 16x16 svgz that is causing a crash on startup in QSvgRenderer then kcalc can add fine. Have you actually tested any of the problems in this report or do I need to go through them one by one? As i said, it enters and endless loop on start, so i did not test anything. KNumber::operator quint64(void) const seems to call itself if you are on a 64 bit machine like i am. Albert Rich. On 11/25/07, Richard Moore [EMAIL PROTECTED] wrote: On 11/25/07, Albert Astals Cid [EMAIL PROTECTED] wrote: A Diumenge 25 Novembre 2007, Richard Moore va escriure: Removing kcalc seems daft to me. It's pretty much essential for a sane desktop. Are you saying there are some problems with it that need fixing or just playing jobsworth? Problem i have: * I can't not start it, it ends up in an inifite loop I'm getting a segfault on startup here, but that seems to be a kiconloader issue. Problem other people has: * It doesn't know how to add http://bugs.kde.org/show_bug.cgi?id=152713 The problems in that bug seem to be more display related. Real problem: * No maintainer No playing here, i'm just not in mood. I'm not playing either, I think we need a calculator. I'll try to look into what's broken it. Rich, ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Removing kregexpedit and kcalc
A Dilluns 26 Novembre 2007, vàreu escriure: On Monday 26 November 2007, Albert Astals Cid wrote: As i said, it enters and endless loop on start, so i did not test anything. KNumber::operator quint64(void) const seems to call itself if you are on a 64 bit machine like i am. So, how about debugging and fixing that issue? My mood is past the line of trying to debug and fix programs i don't know and i don't care, sorry about that. Albert I don`t like to drop kcalc now. For 4.1 we can decide for something else if there is an alternative. A (IMHO) better solution would be to get rid of KNumber and use the C++ library for big numbers. Also fixes a license problem (because GMP is GPLv3, so legally its impossible to ship KCalc at the moment). Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Asking for KTuberling freeze break
Hi, we just got a Christmas theme for KTuberling, it just perfectly fits on the time of the year, the problem is that it breaks the freeze and that there are also some other themes waiting because of the freeze, so either we let them all go in or none (letting only christmas theme does not seem fair to me). Each theme means one string name more to translate. What do you say? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Asking for KTuberling freeze break
A Divendres 07 Desembre 2007, Dirk Mueller va escriure: On Friday 07 December 2007, Albert Astals Cid wrote: Hi, we just got a Christmas theme for KTuberling, it just perfectly fits on the time of the year, the problem is that it breaks the freeze and that there are also some other themes waiting because of the freeze, so either we let them all go in or none (letting only christmas theme does not seem fair to me). Each theme means one string name more to translate. What do you say? I don`t get it. for the next release (which you`re talking about, right?), christmas will be long over. Why adding it then? Right, forgot RC2 was already tagged, will wait for 4.1 Albert Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KCalc's Future
A Dissabte 08 Desembre 2007, Thomas Zander va escriure: On Saturday 08 December 2007 20:00:08 Allen Winter wrote: Hi Bernd, You are listed in kdeutils/AUTHORS as the maintainer for KCalc. Speaking for the KDE 4 Release Team.. I am wondering what your plans are for KCalc in KDE4. There has been a lot of mail going on in kde-core-devel discussing some critical issues with KCalc There have? Can you provide me with a link since I can't find any such mails... I tried a full-text search on 'kcalc' in kmail. and we haven't heard from you. There was one thread on this list which grossly overstated problems (none actually exist anymore) for the app, I didn't expect any mails from bernd myself. So you mean typing 3 + 3 Enter and getting a 0 is the expected behaviour? Albert So, either I'm missing various mails, and in effect the reason for your mail, or this is based on some misunderstandings. In my tests kcalc from svn fits the role of a general purpose desktop calculator perfectly. So your mail surprises me, I'm not sure there is a strong need for a maintainer. Its got well below the average amount of bugs (22) *confused* ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KCalc's Future
A Dissabte 08 Desembre 2007, Christian Ehrlicher va escriure: Albert Astals Cid schrieb: A Dissabte 08 Desembre 2007, Richard Moore va escriure: On 12/8/07, Albert Astals Cid [EMAIL PROTECTED] wrote: So you mean typing 3 + 3 Enter and getting a 0 is the expected behaviour? As I said in the previous discussion this works fine here. It only seems to be an issue for people on 64 bit machines, and I suspect not even all of those. If people would get together info about things like which version of gmp they're using, which compiler etc. then maybe we could make some progress on this issue. I know it's weird, actually i'm using exactly the same configuration (ubuntu version, installed libraries and cpu model) than John Tapsell and it works for him. I've already volunteered givin remove access to my machine to David Johnson so he can try fixing the bug but he said it was not necessary. For the record: gmp version: 4.2.1+dfsg-5ubuntu4 g++ version: g++-4.1 (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) machine: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ OpenSuSE 10.3 64bit, gcc 4.2.1 The attached patch fixes the problem (better: avoids the problem). After this 3+3 is 6 again on my system. It was ever, but displaying did not work correct. Works here :-) Albert Christian ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Fwd: Re: [Kde-games-devel] kwin4 rename?
Here is the messate from Martin from one month ago. Albert ---BeginMessage--- So, Martin, what do you think? We could change it to something like: Connect4/Konnect4 (by Maoricio), or simply add s - Kwins4; IF we are to change at all. I think we have discussed this before ~ half a year ago. My statement is still the same: I dont mind the renaming at all if two conditions are met: 1. I dont have to do it ;-))) Anybody can feel free to change the stuff. But please properly, that is code, manual, translations, RC files, ... (and what about e.g. renaming the classes or would you only change the names visible to the user?) 2. Be aware of trademark violations. All these Connect 4 (tm) things are trademarked. So we need a harmless name or someone who researches the actual trademark situation. (Konnect 4 is propably not going to help much in avoiding these violations) PS: Pino, please feel free to foward to the original author of the question (Allen Winter?) if he does not read kde-games ___ kde-games-devel mailing list [EMAIL PROTECTED] https://mail.kde.org/mailman/listinfo/kde-games-devel ---End Message--- ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: What to do about Kompare?
A Dimarts 11 Desembre 2007, Allen Winter va escriure: On Monday 10 December 2007 18:04:16 Kevin Kofler wrote: In Bug 153463 [1], Kevin Kofler provides some patches to make the current Kompare code in kdesk compile (and work, I guess). It definitely works here, at the very least. :-) Kevin, would you want to take over kdesdk/kompare and make it work for KDE4.0.0? Else, I guess we won't have kompare in KDE4.0. Yes, I'm willing to pick it up. Excellent. Great News! Then I suggest you: 1) commit your patches into kdesdk/kompare 2) uncomment the add_subdirectory(kompare) line in kdesdk/CMakeLists.txt Oh,... but before doing that... any idea how many new i18n() strings are in your patches? Give him a powerful bugzilla account and set him as default bug owner too. Albert -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
kwin4 renamed to KFourInLine
Ok, so i renamed from kwin4 to KFourInLine given the kdegames IRC meeting consensus and Martin that is the maintainer agreeing. I'm almost sure i've done everything needed so that it works, i could start a game and play, but obviously double checking everything works as expected is welcome. Non user visible strings like classes names and stuff have not been changed (i'm not THAT crazy) Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
GStreamer backend on kdebase
Vir says it does not work and it's not expected to work. So i ask myself why is it sitting in the place of the code we are going to release in less than one month. Can we please move it to somewhere were it should belong like playgound now that all the marketing buzz has been done and not bring it back until it sort of works? Albert P.S: Obviously i'm inmensely grateful to TT for giving us working Phonon backends on all platforms and for making it in a more open way and all that stuff, but that does not makes them able to not follow guides, and we are on a release mode and importing non-working code to the release branch is just plain wrong on my scale of things. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: tags/unmaintained/4 tags/unmaintained/4/khexedit trunk/KDE/kdeutils/khexedit trunk/KDE/kdeutils/khexedit/parts [POSSIBLY UNSAFE]
A Dimecres 02 Gener 2008, Tom Albers va escriure: Op woensdag 2 januari 2008 01:44 schreef u: No idea? Will just svn r(e)m(ove) it then, on Wednesday night, if noone minds and update the process_orphans.txt with delete messages/kdeutils/khexedit.po Yes please. I did it, as it is needed to have a full l10n-kde4 checkout Just saw, I forgot kdeutils/doc/khexedit, oh well. Were should this dir go? tags/unmaintained/4/doc? Or better tags/unmaintained/4/khexedit/doc? tags/unmaintained/4/khexedit/doc please. Done too. Albert Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: tags/unmaintained/4 tags/unmaintained/4/khexedit trunk/KDE/kdeutils/khexedit trunk/KDE/kdeutils/khexedit/parts [POSSIBLY UNSAFE]
A Dimecres 02 Gener 2008, Friedrich W. H. Kossebau va escriure: Am Mittwoch, 2. Januar 2008, um 14:54 Uhr, schrieb Albert Astals Cid: A Dimecres 02 Gener 2008, Tom Albers va escriure: Op woensdag 2 januari 2008 01:44 schreef u: No idea? Will just svn r(e)m(ove) it then, on Wednesday night, if noone minds and update the process_orphans.txt with delete messages/kdeutils/khexedit.po Yes please. I did it, as it is needed to have a full l10n-kde4 checkout Thanks. Why is the full checkout needed? Is the script run locally? http://techbase.kde.org/index.php?title=Schedules/KDE4/4.0_Module_Status#i1 8n doesn't say so. Well, it says, one needs the templates and scripts folder. And even then: Isn't it enough to just checkout the module folders, in this case templates/messages/kdeutils/ and templates/docmessages/kdeutils/ and do the modification? What text should I add to techbase, then? Well, the process_orphans.sh script is not run automatically, so to apply the changes done in it you need to have the full checkout. Albert Friedrich ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Removing settings:/ ioslave ?
Hi, as of now, settings:/ ioslave it is not working, if you look at its code, the listings of the settings:/ ioslave comes from the contents built at buildsycoca state of what it is defined in the Settings/ submenu entry defined by kde-settings.menu The problem is that right now, kcm entries are not Type=Application anymore, they are now Type=Service so they are not taken into account in menu building time so what you get in settings:/ is the KDE3 kcm if you have any or nothing otherwise. Actually i think that the current state is unfixable because the only way of fixing settings:/ that i can think of is basically rewriting it not to use the Settings/ menu defined in kde-settings.menu and instead using whatever systemsettings does to get the categories and kcm, but that is too much for 1 day we have until the tagging. So basically i'm requesting for permission to remove it and for a suggestion of what to do with the nice settings:/ link we have in konqueror start page. Albert P.S: This is all based on my and Rafael (ereslibre) understanding of the code, that can be totally wrong and might be easily fixable, but this is the best we could do while trying to understand kio_settings ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Konqueror first page links to media:/
That does not exist!!! Releasing KDE 4.0 like that is a bad idea, any taker? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Tagging Freeze for KDE 4.0.0
A Divendres 04 Gener 2008, Rafael Fernández López va escriure: On Thursday 03 January 2008 21:08:50, Tom Albers wrote: Reminder: Today (2008/01/03) at midnight UTC we start the Tagging Freeze for KDE 4.0.0. Only allowed changes: compile fixes; *reviewed* fixes of blocker bugs; changes needed to build the release tarballs. Please update your application version numbers today for a 4.0.0 release. For the translators: please no more translations permitted either. We will let you know when trunk is open again for 4.0.1 bug-fixing. The Release Team. The problem with KPluginSelector has been fixed (that one was a blocker). Green light for tagging. The problem was that a bunch of .desktop files were translating a should-not-be-translated X-KDE-PluginInfo-Category field. I completely disagree here, X-KDE-PluginInfo-Category is clearly defined as translatable in ~/l10n-kde4/scripts/createdesktopcontext.pl so it's your problem asuming a field would not be translated when it is. Albert Now all of them are fixed, all KDE modules (from kdelibs to extragear and playground). Bye, Rafael Fernández López GPG Fingerprint: B9F4 4730 43F8 FFDD CC5E BA8E 724E 406E 3F01 D070 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.0.x planning
A Dilluns 07 Gener 2008, Dirk Mueller va escriure: Hi, are there any opinions about 4.0.x release plans already? I would like to schedule 4.0.x releases in roughly monthly schedule, beginning with ~ end of the month. I agree, monthly updates seems a good idea to me. Albert Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Move kwalletmanager?
A Dimarts 15 Gener 2008, vàreu escriure: On Tuesday 15 January 2008 14:51:46 Allen Winter wrote: But I still think we need module coordinators for kdebase, kdeutils and kdetoys. Perhaps we should put out a help wanted? Makes sense to do that, yes. The thing with a list like this is that the people on it tend to be swamped by work already... Idea; what about Albert post a blog about his experiences of becoming a coordinator for l10n? I'm hoping its not too much of a horror story, naturally, but some positive feedback on the job will surely help others step up. Albert; you up for that? :) Well, i'm not sure i can not make it not to be an horror story, but imho l10n is a bit special as most commiters are not very knowledgeable people, etc, but i will try to see it from the bright side, tomorrow though. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Extragear plasma for 4.0.1
A Dissabte 26 Gener 2008, Tom Albers va escriure: Hi, I asked on IRC, but got no direct answer. What is the policy for extragear-plasma? Is it based on trunk or the branch. In other words, do I need to make a tarball for 4.0.1 or is 4.1.0 the next time a tarball will be available for the users? There is no extragear KDE4 branch so extragear-plasma from trunk is already using trunk plasma API that if changed makes them incompatible with 4.0, right? Albert Best, Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Initial revision of KDE 4.1 schedule available on Techbase
A Dimecres 13 Febrer 2008, Dirk Mueller va escriure: On Saturday 26 January 2008, Matt Rogers wrote: I've posted a new schedule on http://techbase.kde.org/index.php?title=Schedules/KDE4/4.1_Release_Schedu le that should work as the nearly final release schedule. Feedback is appreciated. I have a couple of questions: a) Binary compatibility is not required. what do you mean by that? you're saying that newly added features do not have to be binary compatible? you're saying that binary incompatible changes are allowed in kdelibs? For me it means, it is not required to maintain binary compatibility of new classes added in the 4.0-4.1 timeframe. Albert b) Why a hard feature freeze for alpha1, e.g. before any user announced release? that doesn't make sense. we should have alpha releases that attract user attention and be able to react to the feedback, which often means changing or implementing new features. imho the feature freeze shouldn't be before beta1 or beta2. c) Why a message freeze before beta1? bugfixes often require message changes. And translators often need time to translate things. And we are quite kind guaranteeing exceptions. Albert d) it is still a mis-aligned schedule, however I'm not going to complai too loudly about it given that it might slip by one month and then be aligned :) e) I like the no-new-artwork freeze. Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.0.2 tarballs ready
A Dijous 28 Febrer 2008, Dirk Mueller va escriure: Hi, KDE 4.0.2 tarballs have been uploaded. The plan is to release them Tuesday/Wednesday next week. Let me know if you find any issues with them. kde-l10n failed to build as usual, I'm currently fixing it. Do you actually call this a bug report? Or does the release dude position guarantee a carte blanche to say things suck without providing further information? Something like pl/docmessages/kdebase-workspace does not build would be more than enough. Albert Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: kdesupport branch for 4.0.x
A Divendres 21 Març 2008, Andreas Pakulat va escriure: On 21.03.08 13:46:24, David Faure wrote: On Friday 21 March 2008, Andras Mantia wrote: without hunting on project pages for the latest release that works with a specific KDE version. Does this mean that those libs in kdesupport are making incompatible changes !?? Sorry, I didn't follow the kde-devel thread -- but if the latest version of the libs doesn't work then it means they are not keeping SC/BC... No, its not about the libraries keeping BC/SC. In this particular case soprano just switched to Qt4.4 as dependency due to using Qt4.4-only API. And this obviously leads to confusion, unless there's a complete 4.0-branch for kdesupport. You can always use a released version like soprano 2.0, right? Albert Andreas ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
About okteta
Hi Friedrich there is a oktetapart.pot both on kdeutils and playground-utils i had a look and seems there is some code that is duplicated. Is this known and will be fixed or it's a leftover and should be removed? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: finishing the spring cleanup of kdeutils
A Diumenge 04 Maig 2008, Friedrich W. H. Kossebau va escriure: Hi, I just moved klaptopdaemon, kmilo and ksim from kdeutils to unmaintained/4, as noone has been found to take care of that codebase. Could someone from the i18n-team take care of the translation files, please? (BTW: Is it sufficient to write this request for taking care of the translation files just to the release-team, or should one also cc: i18n ?) More than enough, doing nothing is enough too as the scripty log will begin to complain about .pot files that are not generated anymore, but if you warn, the better. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: breaking BIC for new addon libs in minor releases (was: Re: Goals? How are we doing?)
A Dimarts 06 Maig 2008, Tom Albers va escriure: Op dinsdag 06 mei 2008 18:30 schreef u: I disagree. I think it is a must to be BC between minor releases. For everything? Yes. I disagree, this was never a promise we made outside kdelibs + kdepimlibs + maybe kdebase-runtime. I agree it is good not changing SC/BC for the sake of doing it but let's not make things imposible to work, or do you want libokteta (e.g) to virtually be forked until KDE5 if current api is not good enough? Albert If you want to be bic public, go to extragear/libs untill you are ready... What would this change for 3rd-party developers? You can make a release whenever you like and bump the major so version of the lib as you like in each release. For me it would be more work, as I would have development spanned between extragear/libs and kdeutils. And it would add an additional (if only soft) dependency between modules. No, as long as you make releases from the library, it's is just another 'external' dependency. As long as it is not a cyclic dependency as we now face with libkipi, it is not a problem. Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Non KDE urls in KDE programs
Hi, today i came across a text in Kubrick (Rubicks cube kdegame) (made by Ian in the CC) that says The 'Beginner Solution' demonstrated here is from www.geocities.com/jasmine_ellen/RubiksCubeSolution.html (see that site for a full description and other solution ideas). Just over 100 moves solve a cube that is shuffled in 20. I'm not really sure that linking to that geocities page is correct. Resons: * We don't know who controls that page, it might end up converted in a children porno/nazi propaganda/watheverYouHateMore page. * The page might disappear (as it is now, that is down) So if we feel we really need to provide such a description on how to solve the cube i propose to write a similar one and host it in games.kde.org. And why am I mailing to the release team? I'd want to know which is the opinion of people on having a policy that advises against linking to non kde.org links. Albert P.S: You can see page contents on archive.org http://web.archive.org/web/20070718183141/peter.stillhq.com/jasmine/rubikscubesolution.html ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: extragear/plasma is now kdeplasmoids
A Dimarts 27 Maig 2008, Dirk Mueller va escriure: Hi, I've moved extragear/plasma to KDE/kdeplasmoids. This has the following benefits: a) it will be branched together with KDE, which means that we can ship bugfixes for stable releases without dragging in new dependencies/features/strings/api usage b) we can translate it and ship translations together wtih KDE releases c) there are regular releases of it automatically with the patch releases starting with KDE 4.1.1 and so on, which happen monthly and are in line with corresponding plasma changes in kdebase-workspace d) the build dependency cycles introduced by the move of the nowlistening plugin to kdebase-workspace is fixed. As a result of that, translations need fixup, I think i did all necessary, let's wait for next scripty run to be sure though. Albert and the nowlistening plugin must move out of kdebase-workspace. Thanks, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.10
A Divendres 27 Juny 2008, Sebastian Kügler va escriure: On Friday 27 June 2008 14:18:22 Stephan Kulow wrote: I asked the packagers the last days and there seems to be still high interest in the KDE 3.5 branch. 4 months have passed by now since 3.5.9 release and I would give it after KDE 4.1 and then release 3.5.10 mid of august. What do you think? +1, but has anything significant changed in this branch lately? I fixed a crash in kpdf the other day. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Away in holidays
I'll be away on holidays from 4th of July to 19th of July missing tag of RC 1 and being very close to tag of KDE 4.1 final. I've spoken to Pino and he has agreed he'll be taking my role as l10n coordinator between those dates. I hope the release team is confortable with this situation as Pino is as or more knowledgeable than me and you all know him well. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: show stopper list?
A Dilluns 21 Juliol 2008, Cyrille Berger va escriure: On Monday 21 July 2008, Pino Toscano wrote: Is it so difficult having the cooperation of Trolltech in this regard? Or things won't work if we (KDE) don't do the daily poking game? Well, I have to remind you that Qt is an open source product that we use free of charge, and we should treat it as it, and behave toward TT the same way we expect our bug reporters/users to behave toward us, either be nice, or provide a patch. How many times have you provided a patch to TT and got it accepted? I have a quite negative track on that. And BTW this is quite off topic on this list. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
KDE 4.1.x schedule
We need to plan the 4.1.x schedule. There have been some translation team leaders asking me if it was worth translating stable branch as no 4.1.x release was annouced on http://techbase.kde.org/Schedules/KDE4/4.1_Release_Schedule Tom Albers has suggested getting the last tuesday of each month for the release and substract a week to find the tag date If everyone is OK with that i can update the wiki. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.1.x schedule
A Diumenge 27 Juliol 2008, Aaron J. Seigo va escriure: On Sunday 27 July 2008, Albert Astals Cid wrote: We need to plan the 4.1.x schedule. There have been some translation team leaders asking me if it was worth translating stable branch as no 4.1.x release was annouced on http://techbase.kde.org/Schedules/KDE4/4.1_Release_Schedule Tom Albers has suggested getting the last tuesday of each month for the release and substract a week to find the tag date If everyone is OK with that i can update the wiki. sounds sensible to me =) I've added .1 .2 and .3 to http://techbase.kde.org/Schedules/KDE4/4.1_Release_Schedule now Of course they can be changed but i want something there to make sure noone gets the wrong idea about not having any 4.1.x release Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Extragear KDE 4 stable branch
A Dilluns 04 Agost 2008, Tom Albers va escriure: Op maandag 04 augustus 2008 09:46 schreef u: What's wrong with /branches/stables/extragear/ ? I think it will only contain really stable releases, i.e., those kde3 releases. In that case that folder can be renamed to extragear-kde3 and recreate the extragear folder. To me this would be a no-brainer. Well, i'm both fine with branches/stable/extragear-kde3 branches/stable/extragear-kde4 or branches/stable/extragear branches/stable/extragear-kde4 or branches/stable/extragear-kde3 branches/stable/extragear BUT i think the second one would fit more with what we currently have branches/stable/l10n - kde3 branches/stable/l10n-kde4 - kde4 There's no need in invalidating everyone's already checked out paths. Albert Best. Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Schedules page for extragear modules
Hi, at the translation team we have a problem that translators never know which branch they have to translate for extragear applications because actually we have stable and trunk for KDE3 and stable and trunk for KDE4 so for example for konversation next release is kde3 trunk based but for amarok is kde4 trunk based and for ktorrent is kde4 stable So it would be cool if extragear maintainers would write in that page in which page their new release will be. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Schedules page for extragear modules (now with url!)
El Monday 11 August 2008 03:12:08 Ian Monroe va escriure: On Sun, Aug 10, 2008 at 5:43 PM, Albert Astals Cid [EMAIL PROTECTED] wrote: Hi, at the translation team we have a problem that translators never know which branch they have to translate for extragear applications because actually we have stable and trunk for KDE3 and stable and trunk for KDE4 so for example for konversation next release is kde3 trunk based but for amarok is kde4 trunk based and for ktorrent is kde4 stable So it would be cool if extragear maintainers would write in that page in which page their new release will be. Albert What page? Woa, such a long mail and you read it to the end, thanks :-) http://techbase.kde.org/Schedules/Extragear Albert Ian ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [Kde-extra-gear] Schedules page for extragear modules (now with url!)
El Tuesday 12 August 2008 21:38:47 Joris Guisson va escriure: The ktorrent 3.1 (for KDE4) branch is now in stable (branches/stable/extragear/network/ktorrent), but the directory branches/stable/l10n-kde4/templates/messages/extragear-network doesn't exist yet. Previously the stable branch was still for KDE3, so somebody needs to make sure that the templates are generated in branches/stable/l10n-kde4/templates/messages/extragear-network and not in the directory for the kde3 stable translations. Man i'm so sorry i forgot to create branches/stable/extragear-kde4/network Could you please move ktorrent stable there? Sorry again. Albert Joris, On Mon, Aug 11, 2008 at 10:04 AM, Albert Astals Cid [EMAIL PROTECTED] wrote: El Monday 11 August 2008 03:12:08 Ian Monroe va escriure: On Sun, Aug 10, 2008 at 5:43 PM, Albert Astals Cid [EMAIL PROTECTED] wrote: Hi, at the translation team we have a problem that translators never know which branch they have to translate for extragear applications because actually we have stable and trunk for KDE3 and stable and trunk for KDE4 so for example for konversation next release is kde3 trunk based but for amarok is kde4 trunk based and for ktorrent is kde4 stable So it would be cool if extragear maintainers would write in that page in which page their new release will be. Albert What page? Woa, such a long mail and you read it to the end, thanks :-) http://techbase.kde.org/Schedules/Extragear Albert Ian ___ Kde-extra-gear mailing list [EMAIL PROTECTED] https://mail.kde.org/mailman/listinfo/kde-extra-gear ___ Kde-extra-gear mailing list [EMAIL PROTECTED] https://mail.kde.org/mailman/listinfo/kde-extra-gear ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.10
A Dimarts 19 Agost 2008, Stephan Kulow va escriure: Am Dienstag 19 August 2008 schrieb Benoit Minisini: On mardi 19 août 2008, Stephan Kulow wrote: Am Montag 18 August 2008 schrieb Sebastian Kügler: On Wednesday 13 August 2008 12:53:21 Stephan Kulow wrote: I will tag KDE 3.5.10 on tuesday, 19th and prepare tars for the packager. As the general interest in this release should be pretty limited, it will be in the hands of the promo team when the announcement fits best in the line of dot posts ;) I guess by next Tuesday, it's less likely to be snowed under by the flurry of Akademy posts, and journalists had some breathing time as well. (I saw news sites with 2/3s of their frontpage articles being about KDE / Akademy :). So let's target Tuesday, 26th, noon-ish. You can start synching in the morning then, and I'll have you confirm on IRC whether everything is in place. OK? Tuesday noon-ish is bad, I have Krabbelgrubbe between 9 and 11 :) But we talk on monday evening. Greetings, Stephan Hi, I'm currently committing a not important patch to kicker for KDE 3.5.10. When exactly KDE 3.5.10 will be tagged? Is it possible to delay the tagging for one day or two? No. 3.5 branch is frozen since ages - I'm just packaging it for the fixes in the branch. Well, he's been adding changes like made lately so imho either we revert all his changes or let him finish them. Albert Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: kdesupport Policy
A Dissabte 23 Agost 2008, Allen Winter va escriure: Howdy, The recent build problems in our kdesupport package dependencies needs to be addressed. I think we need to treat kdesupport libs just like any other external dependency. Something like the following guidelines: No KDE code (in trunk) changes should be necessary until: - a real release of the kdesupport package has been made AN - that release has been packaged by the major distros AND - an announcement about the needed upgrade is made in advance AND - people have had time (30 days?) to upgrade to the new packages For example: libfoo v1.0 is released. kde-packagers are notified to please provide packages for their distros. kde-devel and kde-code-devel are notified that within 30 days their builds will fail unless they have libfoo v1.0 installed -- that the distros have been notified and we hope packages will start appearing soon. People wanting to develop against libfoo v1.0 will need to do so in a work branch. Or using nice #ifdefs like we do in okular with poppler. Albert I need to get out of the habit of building kdesupport all the time -- we should be relying on distro packages where possible. Comments? ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.final?
A Dilluns 25 Agost 2008, Stephan Kulow va escriure: Am Montag 25 August 2008 schrieb Allen Winter: On Monday 25 August 2008 08:35:02 Stephan Kulow wrote: Am Montag 25 August 2008 schrieb Aaron J. Seigo: while it might be best to have everyone's hands on KDE4, it's also realistic that there will be those who remain interested in KDE3 for various reasons and there's no reason to try and control that beyond encouraging KDE4 to be the primary focus. as it already is for virtually Actually I think the best way to let people focus on KDE4 is making sure KDE3 becomes unusable as stable platform in allowing untested experiments. At least I'm sure that KDAB tests kdepim changes and is around to help fix and port stuff. So people who need kdepim 3.5 could conceivably switch to the kdepim/enterprise branch. I don't have an issue with kdepim 3.5.17 being released. But I do have one with kdelibs or kdebase changes based on experiments. And actually kdepim was one of the modules I had to fix up before it would compile. BTW Coolo went to the facts way and disable message extraction for all KDE modules of 3.5 except kdepim, so if we decide we let people still work on them, message extraction for translators should be reenabled. Albert Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
More KDE 4.1.x releases?
Today we are supposed to get the tagging of 4.1.3 and techbase says there are no more planned 4.1.x releases, should i instruct translators to start focusing on trunk? Or are we going to have a 4.1.4? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: kdepimlibs Licensing
A Divendres 07 Novembre 2008, Allen Winter va escriure: Howdy, Would it be possible to relax the licensing requirements in kdepimlibs to permit GPL code? Currently, kdepimlibs requirements are the same as kdelibs; i.e. only LGPL, BSD, X11. There are at least 4 GPL libraries in kdepim (libkholidays, libksieve, kdgantt, libkleo) that would be very useful for kdebase, KOffice and extragear. For example: libkholidays could provide holiday info for calendar plasmoids libksieve could allow Mailody to implement IMAP sieve filters kgantt would allow KOffice Gantt charts without having to use the current svn external etc. Attempts at relicensing these libraries has failed or is very difficult. We have tried. I've been told that there was agreement at the last Akademy to allow kdepimlibs to have GPL code?? If wasn't there so this is 3rd hand info. I'd like an official answer. Or another suggestion. Comments? I'm not at all involved in kdepimlibs besides roaming const fixes :D But this is my advice, if you are going to accept GPL libraries in kdepimlibs adding a _gpl suffix to them seems a good idea so people linking know they are linking to a GPL library. Albert -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: kdepimlibs Licensing
A Divendres 07 Novembre 2008, Tom Albers va escriure: Op vrijdag 07 november 2008 00:50 schreef u: A Divendres 07 Novembre 2008, Allen Winter va escriure: Howdy, Would it be possible to relax the licensing requirements in kdepimlibs to permit GPL code? Currently, kdepimlibs requirements are the same as kdelibs; i.e. only LGPL, BSD, X11. There are at least 4 GPL libraries in kdepim (libkholidays, libksieve, kdgantt, libkleo) that would be very useful for kdebase, KOffice and extragear. For example: libkholidays could provide holiday info for calendar plasmoids libksieve could allow Mailody to implement IMAP sieve filters kgantt would allow KOffice Gantt charts without having to use the current svn external etc. Attempts at relicensing these libraries has failed or is very difficult. We have tried. I've been told that there was agreement at the last Akademy to allow kdepimlibs to have GPL code?? If wasn't there so this is 3rd hand info. I'd like an official answer. Or another suggestion. Comments? I'm not at all involved in kdepimlibs besides roaming const fixes :D But this is my advice, if you are going to accept GPL libraries in kdepimlibs adding a _gpl suffix to them seems a good idea so people linking know they are linking to a GPL library. Albert dfaure pointed out that that would break bc... Why? Those libraries that would get the gpl suffix are not public at the moment, so there's no bc to maintain, right? Albert Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Killing trunk/kdekiosk
It seems it's old as three years, can me move it to unmaintained to not confuse people (translators amongst them) ? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: reopen trunk for KDE 4.3?
A Dijous 04 Desembre 2008, Aaron J. Seigo va escriure: On Wednesday 03 December 2008, Tom Albers wrote: Op Wednesday 03 December 2008 23:17 schreef u: Hi, I know we haven't implemented the whole always summer in trunk scheme, but I wonder if we can go ahead and branch KDE 4.2 and reopen trunk. Just for kopete alone, I have 3 patches, and a whole new protocol support plugin to integrate and I'm sure other projects would benefit from this as well. Thoughts? The problem is that we are only setup to handle two active branches for the translations. Currently 4.1 and 4.2, if we branch off 4.2, we need to setup a third branch for translations. or would it make sense to ignore trunk until 4.2 is released for translations? so that the two branches being tracked would be 4.1 and the upcoming 4.2? for that matter, why are thranslations still being tracked for 4.1 when 4.2 is now in string freeze? Because 4.1.4 is planned for tagging in 10th of december[1]. should translators not be working on 4.2? (Honest questions, i know next to nothing about the translation procedures) Who says they are not working on trunk? For example, in 5 hours there have been 3 commits to the 4.1.x translation branch and 19 to trunk translation branch. Albert [1] http://techbase.kde.org/Schedules/KDE4/4.1_Release_Schedule So, just in my personal opinion, we can drop 4.1.4 and spent our energy to 4.2.0. +1 from me, for the imho good reasons you outline. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Qt4.5?
A Diumenge 21 Desembre 2008, Tom Albers va escriure: Hi, I see on IRC the question if we depend on 4.5 for the 4.2.0 release. What should be my answer? Qt 4.5 hasn't been released yet. So how can we depend on it? Albert Best, Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: adding strings to fix bugs?
A Dijous 25 Desembre 2008, Matt Rogers va escriure: Hi, Can we add new strings in order to fix bugs or are those strings covered as part of the string freeze? Also, Is there a techbase page that defines what the string freeze rules are? I couldn't find one by searching for string freeze on techbase. The rules are you ask in kde-i18n-...@kde.org explaining why you need a new string and which string[s] would be and you get the ok/ko from the translators. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
A Dissabte 03 Gener 2009, Tom Albers va escriure: Hi, I've put up a schedule for 4.3. As we have Akademy on 3rd of July, I've planned to have released RC1 by that date, as we branch at that stage, trunk is open for features during Akademy. I've cancelled the Alfa release, as it brings almost no feedback. We can add it to the schedule later on when we see some massive code changes in 4.3, which warrants an extra release. Let me know when the schedule is wrong for some reason. http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule I'ld like to announce this schedule to k-c-d by the end of next week. An artist complained to me today that the Artwork freeze is after the Message freeze but most of the times new Artwork needs new Messages so either we add an explicit allowance for breaking the Message freeze or we add an explicit warning that the Artwork Freeze can't touch any Message. Albert Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
A Dilluns 05 Gener 2009, Tom Albers va escriure: Op maandag 05 januari 2009 01:00 schreef u: A Dissabte 03 Gener 2009, Tom Albers va escriure: Hi, I've put up a schedule for 4.3. As we have Akademy on 3rd of July, I've planned to have released RC1 by that date, as we branch at that stage, trunk is open for features during Akademy. I've cancelled the Alfa release, as it brings almost no feedback. We can add it to the schedule later on when we see some massive code changes in 4.3, which warrants an extra release. Let me know when the schedule is wrong for some reason. http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule I'ld like to announce this schedule to k-c-d by the end of next week. An artist complained to me today that the Artwork freeze is after the Message freeze but most of the times new Artwork needs new Messages so either we add an explicit allowance for breaking the Message freeze or we add an explicit warning that the Artwork Freeze can't touch any Message. I think the l10n people should decide if the exception is ok. If not we need to go for the explicit warning. Can you bring it up on the l10n ml? Done, waiting for feedback. Albert Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.2.0 tarballs (non-final, try #1) (Dirk Mueller)
A Dijous 22 Gener 2009, Mauricio Piacentini va escriure: You guys are probably aware of this, but I did not see scripty running for the past couple of days, so translation of .desktop files has not been updated afaik. It is important to have at least one more pass before the tagging, imo, as I understand the .desktop file entries are used for the menus, right? At least it is what I am seeing here with pt_BR. Having a look at kdelibs 4.2 branch scripty commited changes on r914644 | scripty | 2009-01-21 14:40:16 +0100 (dc, 21 gen 2009) | 1 line r914107 | scripty | 2009-01-20 14:20:56 +0100 (dt, 20 gen 2009) | 1 line r913548 | scripty | 2009-01-19 15:10:42 +0100 (dl, 19 gen 2009) | 1 line r912909 | scripty | 2009-01-18 14:23:59 +0100 (dg, 18 gen 2009) | 1 line r911978 | scripty | 2009-01-16 14:30:09 +0100 (dv, 16 gen 2009) | 1 line r911494 | scripty | 2009-01-15 14:55:52 +0100 (dj, 15 gen 2009) | 1 line So it seems it's been working quite reliably, what files did you expect to get updated and did not? Albert Regards, Mauricio Piacentini ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.2.0 tarballs (non-final, try #1) (Dirk Mueller)
A Divendres 23 Gener 2009, Mauricio Piacentini va escriure: Albert Astals Cid wrote: Having a look at kdelibs 4.2 branch scripty commited changes on r914644 | scripty | 2009-01-21 14:40:16 +0100 (dc, 21 gen 2009) | 1 line r914107 | scripty | 2009-01-20 14:20:56 +0100 (dt, 20 gen 2009) | 1 line r913548 | scripty | 2009-01-19 15:10:42 +0100 (dl, 19 gen 2009) | 1 line r912909 | scripty | 2009-01-18 14:23:59 +0100 (dg, 18 gen 2009) | 1 line r911978 | scripty | 2009-01-16 14:30:09 +0100 (dv, 16 gen 2009) | 1 line r911494 | scripty | 2009-01-15 14:55:52 +0100 (dj, 15 gen 2009) | 1 line So it seems it's been working quite reliably, what files did you expect to get updated and did not? You are right, false alarm! I was not seeing the updated translations showing up in .desktop files, but that is because I was observing trunk by mistake. I guess you guys switched scripty to update the 4.2 branch (of course) and trunk will be updated again in the future, after the release, right? Exactly Albert Regards, Mauricio Piacentini ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: About Kamala
A Monday, 13 of April de 2009, Mauricio Piacentini va escriure: Albert Astals Cid wrote: playground still has this meaning but afair we changed extragear to stuff that will be released in its own schedule OR does not fit in what we think are essential programs of a desktop For the second range of programs there is the config.ini file in playground/utils/createtarball that lets you add your program for release inside the extragear release that happens at the same time of KDE releases. So in this case I think Kamala can live in extragear, and be released aligned with KDE. I looked at the tree and could not find a suitable directory, though. Should it be extragear/other, or extragear/misc? extragear/misc is ok me. Albert We can later discuss then if our kdegames approach of letting lots of games in is still valid, given this fact. Maybe we should consider moving some to extragear/games, which does not exist currently. Regards, Mauricio Piacentini ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.3 RC1 preparations
A Dimarts, 23 de juny de 2009, Dirk Mueller va escriure: On Tuesday 23 June 2009, Albert Astals Cid wrote: c) announce to kde-cvs-announce when the branching happened and what the next steps are. I would like to avoid branching l10n-kde4 for now, but that means that we have to change the documentation externals again, or hope that nobody touches the documentation after branching. Any comments? Why would you want to avoid branching l10n-kde4? Hmm, no particular reason, it is just work. I can start with moving branches/stable/l10n-kde4 to branches/KDE/4.2/l10n-kde4 and then copying trunk/l10n-kde4 to branches/stable/l10n-kde4 together with branching KDE 4.3. Does that sound fine? do you have time to help me reviewing/fixing the scripty setup for that? Yep, tomorrow is holiday here and i don't have nothing to do (go geekness! go!) so i can probably help. Albert Thanks, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
kdevelop and kdevplatform tagged in branches/KDE/4.3
I wonder if they really belong there, can someone clarify? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Permission Request to Backport a Desktop File Addition to kdebase 4.3
A Dimarts, 30 de juny de 2009, Fredy Yanardi va escriure: Hello all, I implemented a small feature for konqueror's searchbar plugin[1]. This new feature requires new property in the kdebase's webshortcut searchprovider desktop file, [Suggest] that contains the suggestion service for a specific search provider [2]. Since this request has been committed to the konq-plugins extragear module as well, it will be included in the konq-plugins extragear accompanying KDE 4.3. (KDE extragear has different release schedule, doesn't it?). But if the searchprovider desktop file addition is not in the kdebase 4.3, this feature is just non-functional (but no harm at all). Hence I request to backport the searchprovider desktop file additional property to kdebase 4.3 to make this feature also functional in KDE 4.3. Since it is a property addition to the desktop file, it should not affect any other KDE modules, hence it is harmless. But if it is not allowed, we already have this for 4.4 :) (I still have few TODOs for this feature, one is supporting opensearch) In my opinion we are too late in the process for new features, besides i'm not sure if that'd need new strings to translate but then it would be a double no from my side. Albert Best regards, Fredy Yanardi [1] http://fyanardi.wordpress.com/2009/06/28/hello-world-and-a-little-feature-f or-konqueror/ [2] http://websvn.kde.org/?view=revrevision=988310 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: kdereview maintainership
A Dijous, 23 de juliol de 2009, Tom Albers va escriure: Hi, Just removed my name from the module maintainers table as being the kdereview maintainer. So if anyone wants to pick it up, feel free. Basically it means tracking the stuff that goes in gets announced on k-c-d and after the review period make sure it moves out or back to playground. In any case preventing kdereview becomes a dumping ground. Which will happen without maintainer. So, another fun job up for taking. Thanks for your effort :-) Albert Best, Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Possible 4.3.0 blocker in the Konsole KPart?
A Dimecres, 5 d'agost de 2009, John Tapsell va escriure: 2009/8/4 Aaron J. Seigo ase...@kde.org: - especially with multiple branches synchronization - which leads to bugfixes sometimes not hitting latest 'soon-to-be-stable' branch (4.3 now) or not hitting on time, as developers seem to be devoted to trunk (sometimes even when 4.3 in this case is not released). svn makes this much more difficult than it should be, and as Thiago has opined about on k-c-d a few times we probably do it the wrong way around by backporting instead of fixing in stable and then forward porting. but again, svn makes this impractical. Agreed. I can't get the hang of svn backporting, and so I simply never do it. With git, on the other hand, I backport daily. It's so natural and easy to bug fix in stable and forward port, while simultanously adding features in the new branch. Once we have git, I'd like to see this issue revisited. I would prefer that KDE got a reputation of releases when ready. So we never release? No thanks. Albert Just start skipping the release that we currently call .0. John ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
KAdrresbook and KContactmanager
Today KAdrresbook was replaced by KContactmanager that got then renamed to KAdrresbook. I have two complaints here: * i18n team was not notified so we faced a weird situation in which kcontactmanager.po disappeared and all translations in kaddressbook.po got changed. We are in process of fixing it but it would make easier if people followed the rules and wrote either kde-i18n-doc, kde-core-devel or this list when moving files. * All bugs from bugs.kde.org have been removed, does this essentially mean that we just released kaddressbook for 4.3 but we are not accepting bugs for it anymore? How cool we are :-/ Besides this the votes per user/maximum votes per bug/votes to confirm values don't match KDE defaults Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KAdrresbook and KContactmanager
A Dimecres, 5 d'agost de 2009, Aaron J. Seigo va escriure: On Wednesday 05 August 2009, Albert Astals Cid wrote: Today KAdrresbook was replaced by KContactmanager that got then renamed to KAdrresbook. you probably want to email kde-...@kde.org (where they are alread discussing the bug closing situation, but not the i18n issues) Wasn't this list about coordinating people? I write here and whoever is coordinating kdepim moves my words to the proper people. I really don't have time to engage in a battle about this issue. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
KDE 4.4 Schedule
I have some people already asking me about the 4.4 schedule, do we have an answer to that other than the blank page in http://techbase.kde.org/Schedules/KDE4/4.4_Release_Schedule ? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.4 Schedule
A Diumenge, 9 d'agost de 2009, Olivier Goffart va escriure: Le Friday 07 August 2009, Tom Albers a écrit : At Friday 07 August 2009 09:03, you wrote: Le Friday 07 August 2009, Allen Winter a �crit : On Thursday 06 August 2009 2:02:07 pm Albert Astals Cid wrote: I have some people already asking me about the 4.4 schedule, do we have an answer to that other than the blank page in http://techbase.kde.org/Schedules/KDE4/4.4_Release_Schedule ? Not yet. Guess we should start discussing. I assume everyone is still ok with the 6 month cycle? (except annma, of course). Please respond with any release date blockers you may know about in early 2010. ie. sprints, meetings, conferences, .. let's block-off known bad dates first. Do we want to depends on Qt 4.6 or not? Few new feature of Qt Q 4.6 that might be interresting for KDE include: state machine API, animation API, graphics effects, webkit improvement in case we want the webkit part, mouse gestures, and more. There is no official date for the release of Qt 4.6, but it should be should be end of 2009 or early 2010. The alpha (technology preview) is planed in september. So Qt seems to be schedguled a little bit before KDE. But Qt can possibly be delayed if Nokia's QA think the release is not ready, and we should not forget that if we want to include new features, trunk (or at least part of it) should start depending on Qt 4.6 earlier in the development process. Is it OK if trunk depends on alpha or beta of Qt? (we already did in in KDE 4.1) Maybe it is an idea to team up with Qt and try to release on the exact same day? Can give both a bunch of added publicity and would be nice to try. To let that work we might want to be a bit flexible on the release date I guess. We can do that. But we need to set a max date on which we are going to release anyways, even if Qt is not ready yet. In return we need to know from Nokia something like two weeks before they are going to release (but then we depend on a TP of 4.6 for the 4.4.0 release, so might want to do a 4.4.1 quickly after that). The advantage is not purely the big news splash but also an immediate real-world showcase for Qt 4.6. The Qt release could as well be in november which would be way too early to release kde in the sme time. Also Nokia probably doesn't want to depends on possible KDE showstoper that could delay the kde release for the qt release. The same applies for KDE, i'm sure we don't want to delay KDE release because a showstoper delays Qt release. More when the Qt release is unscheduled, so i'd say unless Qt 4.6 releases something in November or so we shouldn't even think on depending on it. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.3.1 tarballs uploaded (try #1)
A Diumenge, 30 d'agost de 2009, Pierre Schmitz va escriure: Am Freitag 28 August 2009 14:03:17 schrieb Dirk Mueller: kde-l10n are still being generated, there will be one additional language here. I'll upload them tonight. kde-l10n-pl does not build due to Entity 'kcontrolcenter' not defined Should compile now (i've removed the offending file (kdebase- runtime/kcontrol/index.docbook)) Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Qt 4.6 KDE 4.4.0
A Dissabte, 26 de setembre de 2009, Tom Albers va escriure: Op Wednesday 23 September 2009 21:41 schreef u: It is time to take a decision about Qt 4.6 KDE 4.4.0. I'ld like to announce the following to kcd and kd next saturday. In the past we decided that these things require two explicit +1's. As those are missing, I won't announce this. As i18n coordinator you have my vote here: +0 I can't see it having any effect on us other than shifting release date (neither bad nor good). Albert Best, Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.3.2 tarballs (try #1) uploaded
A Divendres, 2 d'octubre de 2009, Dirk Mueller va escriure: Hi, I just finished the first build of 4.3.2 tarballs. I think some bits in kde-l10n are failing, need to look at that now. Tarballs should be available in the usual place. Intended announcement is next week Tuesday. FWIW i just build branch l10n translations and it worked like a charm. Albert Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.4 Beta1 Tagging ahead
A Dimarts, 24 de novembre de 2009, Dirk Mueller va escriure: Hi, according to the schedule, we're planning to tag KDE 4.4 Beta1 in two days. Does that sound reasonable to everyone? Any blocking issues? I won't have time to check the l10n packages compile so if anyone can take care of it the better. Sorry. Albert Thanks, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 4.3.5?
A Dijous, 24 de desembre de 2009, Anne-Marie Mahfouf va escriure: On Tuesday 22 December 2009 00:20:44 Allen Winter wrote: Howdy, I think we should have a 4.3.5 release, and this should be the final release in the 4.3 series. thoughts? of course, this depends on Dirk and the promo team's holiday schedule. We should make a decision either way very soon so folks don't waste their time backporting to the 4.3 branch. -Allen I am not sure people backported commits as all I personnally heard was that 4.3 was stopped. Did devels effectively backport to make it worth a new release? I can count 64 commits (not much), some of them important enough like fixing a copyright violation in kstars. Albert Anne-Marie ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: getting rid of kde-l10n
A Dimarts, 2 de febrer de 2010, Rex Dieter va escriure: Hear me out. :) I'm not proposing anything yet, but would like to hear about the pros/cons of 1. status quo: shipping translations separately to software 2. shipping translations alonside (ie, in the same release tarballs) the software. How hard would it be to work toward something closer to 2 for KDE SC? What would be the benefit? Albert -- Rex ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: extragear and playground translations included in l10n tarballs of kde 4.4.0 ?
A Dilluns, 8 de febrer de 2010, Eike Hein va escriure: On 02/08/2010 03:52 AM, Tobias Gerschner wrote: A clarification would be appreciated whether it is intended to ship translations of extragear and playground applications now with the KDE SC . This only applies to the SVN tag, and was presumably done by accident. The 4.4.0 tarballs don't contain the Extragear translations and there are no plans to include them there. Dirk are you going to fix this or want me to do it? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
About KDE l10n 4.4.1 tagging
I've tried to run a validation over i18n compilation but my 4.4.x instalattion is in a worrysome state and have run into some problems with the pt_BR and sk dirs but couldn't say if it was my fault or their fault. so if at the end it was not a problem in my side you might have to delete some index.docbook files in those dirs to make sure it compiles. Sorry about not being able to tell more. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
kde-l10n-sv for 4.4.2 does not compile
You might want to remove sv/kdeedu/kturtle/index.docbook to make it compile. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: kde-l10n-sv for 4.4.2 does not compile
It complains about turtlelang entity not being defined as far as i can remember, the Debian team had the same problem, maybe you built against kdelibs not from 4.4.2? Albert --- El mar, 30/3/10, Dirk Mueller muel...@kde.org escribió: De: Dirk Mueller muel...@kde.org Asunto: Re: kde-l10n-sv for 4.4.2 does not compile Para: kde-packa...@kde.org CC: Albert Astals Cid aa...@kde.org, release-team@kde.org Fecha: martes, 30 de marzo, 2010 10:30 On Monday 29 March 2010, Albert Astals Cid wrote: You might want to remove sv/kdeedu/kturtle/index.docbook to make it compile. whats the error message? strangely it built for me. Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: kde-l10n-sv for 4.4.2 does not compile
A Divendres, 2 d'abril de 2010, Jaroslav Reznik va escriure: On Monday 29 March 2010 09:43:20 pm Albert Astals Cid wrote: You might want to remove sv/kdeedu/kturtle/index.docbook to make it compile. turtlelang should be turtlescript - I've not built it yet, it's just by comparing sv and es. Looks like it was caused by fixing !--Dear translator: please NEVER translate the id or anything inside the tags as they are needed in english by the application. Thanks a lot in advance.-- My suggestion is to remove the file and not fix it, if the translator didn't care to make sure it compiles, that is the first step, you can be sure it is nto even been tested. Albert Jaroslav Albert ___ Kde-packager mailing list kde-packa...@kde.org https://mail.kde.org/mailman/listinfo/kde-packager ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: kde-l10n-sv for 4.4.2 does not compile
A Dissabte, 3 d'abril de 2010, Jaroslav Reznik va escriure: On Saturday 03 April 2010 07:24:19 pm Albert Astals Cid wrote: A Divendres, 2 d'abril de 2010, Jaroslav Reznik va escriure: On Monday 29 March 2010 09:43:20 pm Albert Astals Cid wrote: You might want to remove sv/kdeedu/kturtle/index.docbook to make it compile. turtlelang should be turtlescript - I've not built it yet, it's just by comparing sv and es. Looks like it was caused by fixing !--Dear translator: please NEVER translate the id or anything inside the tags as they are needed in english by the application. Thanks a lot in advance.-- My suggestion is to remove the file and not fix it, if the translator didn't care to make sure it compiles, that is the first step, you can be sure it is nto even been tested. Thanks, seems like the only one correct way - I have a patch but that leads to partially untranslated documentation. CCing kde-i18n-doc, maybe someone could take care about it. Well, i already removed the doc that didn't complain, mailed the translators warning him, mailed the packagers about it, don't know what else you want me to do, but i'm open to suggestions. Albert Jaroslav Albert Jaroslav Albert ___ Kde-packager mailing list kde-packa...@kde.org https://mail.kde.org/mailman/listinfo/kde-packager ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: kde-l10n-sv for 4.4.2 does not compile
A Dissabte, 3 d'abril de 2010, Albert Astals Cid va escriure: A Dissabte, 3 d'abril de 2010, Jaroslav Reznik va escriure: On Saturday 03 April 2010 07:24:19 pm Albert Astals Cid wrote: A Divendres, 2 d'abril de 2010, Jaroslav Reznik va escriure: On Monday 29 March 2010 09:43:20 pm Albert Astals Cid wrote: You might want to remove sv/kdeedu/kturtle/index.docbook to make it compile. turtlelang should be turtlescript - I've not built it yet, it's just by comparing sv and es. Looks like it was caused by fixing !--Dear translator: please NEVER translate the id or anything inside the tags as they are needed in english by the application. Thanks a lot in advance.-- My suggestion is to remove the file and not fix it, if the translator didn't care to make sure it compiles, that is the first step, you can be sure it is nto even been tested. Thanks, seems like the only one correct way - I have a patch but that leads to partially untranslated documentation. CCing kde-i18n-doc, maybe someone could take care about it. Well, i already removed the doc that didn't complain, s/complain/compile mailed the translators warning him, mailed the packagers about it, don't know what else you want me to do, but i'm open to suggestions. Albert Jaroslav Albert Jaroslav Albert ___ Kde-packager mailing list kde-packa...@kde.org https://mail.kde.org/mailman/listinfo/kde-packager ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Features for 4.5
A Divendres, 9 d'abril de 2010, Anne-Marie Mahfouf va escriure: On Friday 09 April 2010 00:56:08 Andreas Scherf wrote: Hallo, i have a feature for kdegames/kbounce which is already on trunk. Who is the maintainer of the feature plan? http://techbase.kde.org/Schedules/KDE4/4.5_Feature_Plan I would like to inform him/her ... Andreas You have a feature: is it a suggestion or a patch (will you code it?) If it's only an idea you have, please send it to bugs.kde.org as a wish to the product KBounce and explain your use case and the feature. Add any mockup,info that can help implement it. If you are ready to code it, I suggest you subscribe to kde-games-devel mailing list where Games developers communicate. Present your feature and ask if you can implement it. Then it'll be added to the feature plan. The feature plan is not a place where users request features, it's a page where developers write what they intend to code. I think he meant he already coded it. Andreas if that's the case, just add it yourself, it's a wiki. Albert Best regards, Anne-Marie ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.4.3 tarballs uploaded (try #1)
A Divendres, 30 d'abril de 2010, Lubos Lunak va escriure: On Friday 30 of April 2010, Dirk Mueller wrote: Hi, I just finished uploading the first set of 4.4.3 tarballs. They seemed to have compiled fine for me over night. Please report any issues you might encounter that justify a retag to me/release-t...@kde.org. These include compile failures or serious regressions. kde4-l10n-nl fails at make install with 'file INSTALL cannot find /usr/src/packages/BUILD/kde-l10n-nl-4.4.3/docs/kdelibs/preparetips/prepar etips.1'. It is because make actually creates tips_ter_voorbereiding.1, so I assume the problem is because the manpage translates the command name itself. You might want to take the fixed docbook from r1121234 Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
KTorrent broke kdenetwork in 4.4
c...@alien:~/prod/branches/KDE/4.4/kdenetwork$ svn up Fetching external item into 'kget/transfer-plugins/bittorrent/libbtcore' svn: Target path '/branches/stable/extragear-kde4/network/ktorrent/libbtcore' does not exist Can anyone fix it? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.4.3 tarballs uploaded (try #1)
A Dimarts, 4 de maig de 2010, Dirk Mueller va escriure: On Monday 03 May 2010, Eric Hameleers wrote: Does that actually compile for you? Because I see these lines still, in it compiles for me now. kde-l10n-nl-4.4.3/docs/kdelibs/preparetips/man-preparetips.1.docbook: command kdeopties/command The kdeopties is translated from kdeoptions but as an instance of the actual command name, it should not have been translated in this location. I can confirm that kdeopties is still part of the new tarball, but this was not fixed in r1121234, which I added to the tarball. I don't see this as a release blocker, is it, i mean it compiles and installs correctly, right? If so it's just a badly translated string that should be reported through the usual channels. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Issue with DocBook XML copy removal
Hi, as part of the project that aims to remove DocBook XML copies from kdelibs, we have found a small issue with backwards compatibility. As explained in old mails, the aim of the project is removing DocBook XML V4.1, V4.1.2 and V4.2 copies in kdelibs and use an externally provided V4.2. This means that when compiling against KDE 4.5, any kde docbook using V4.1.2 docbooks will fail to be generated. Most of the documentation on the KDE repo was already using V4.2 so i understand external programs will mostly copy and paste the correct header from our documentation and will be fine after the change. For those using older versions on 99.99% of the cases the fix is simply updating the header of the docbook (one liner), but we wonder if this change can be considered a source compatibility problem, in my opinion we only promised source compatibility on the code level, but others might disagree, hence this mail. As a side note i want to mention that me, Luigi and Burkhard (not involved in the project per se, but KDE documentation master in my book) agree this is a cheap price to pay for the benefit of freeing us from the embedded copies of DocBook XML. Comments? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Translations branch
A Dijous, 20 de maig de 2010, Frederik Schwarzer va escriure: [Tom Albers - Freitag 21 Mai 2010 00:01:36] hey tsdgeos, Can you swith the translations for edu and pim to the branch? We are still translating for 4.4.4 in branches. This situation is kind of messy and will likely confuse quite a few people. :( What i have switched is the trunk translations to point to 4.5 branch not the stable translations to point to the 4.5 branch. Albert Why are pim and edu not using work branches if they do not like the freeze in trunk? Regards ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Early Branch.
A Divendres, 21 de maig de 2010, Sebastian Kügler va escriure: On Thu May 20 2010 22:08:11 Tom Albers wrote: kdeedu trunk will be then open for 4.6 and 4.5 will be in branches/KDE/4.5/kdeedu (probaly) Please don't. Use a work branch. My other email in this thread contains detailed reasons for this. You are late, we discussed this eons ago and they got the exception by silence acclamation. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE SC 4.6 Schedule
A Divendres, 21 de maig de 2010, Tom Albers va escriure: On Fri, 21 May 2010 12:41:54 +0200, Will Stephenson wstephen...@kde.org wrote: With my distribution hat on I'm wondering when KDE SC 4.6 will come out. Hi Will, If we aim for the end of january, I suggest the schedule below. In trunk/playground/utils/releaseschedule I've just committed an application which can help us create this schedule automatically. If anyone wants to play with different freeze times, feel free, it has loads of settings to fiddle with. Beta testers also welcome :) Proposed 4.6.0 schedule as generated by this application: Thursday, October 28, 2010 - Soft Feature Freeze Trunk is frozen for feature commits that are not listed in the planned feature document. Only bugfixes and the code implementing the listed features are to be committed after this date. The feature list also closes today. Features not already finished or not listed on the planned features page will have to wait until the next KDE SC release. Thursday, November 11, 2010 - Soft Message Freeze All translated messages (GUI strings) are frozen on this date. Only previously untranslated strings or clear errors in strings can be fixed. No major new strings changes should be done. It is ok to remove strings. Exception: Artwork (try to keep the number of new strings low anyways). Exception: Typo fixes can be fixed until Beta2 is released but you have to mail kde-i18n-doc saying you made a typo fix change. Thursday, November 11, 2010 - Soft API Freeze To allow the bindings people to have proper time to do their work in preparation to the final release, the API should now be mostly fixed. Changing API is allowed, but commits have to be cc'ed to the kde-bindings mailinglist. This is including older APIs and newly introduced libraries/APIs. Thursday, November 11, 2010 - Dependency Freeze From this moment on it is not allowed to add new dependencies or bump dependencies versions. It is possible to get an exception for this. Post the patch to reviewboard and add the release-team as reviewer. We will check if the dependency is needed and is available on all platforms. In other words: If you have a feature that requires a new dependency or a version of a dependency that is higher than currently checked for in the build system, you need to have committed this change before this date. Thursday, November 11, 2010 - Hard Feature Freeze Trunk is frozen for all feature commits, even those listed in the planned feature document. Only bug fixes are allowed. Thursday, November 18, 2010 - Beta 1 Tagging Trunk is frozen for beta release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. The usual beta rules apply as soon as the Beta tarballs have been generated. Wednesday, November 24, 2010 - Beta 1 Release The beta becomes available for general consumption. Monday, November 29, 2010 - Documentatin Freeze No more substantive changes to documentation or handbooks after this date. Typos, spelling and simple grammar changes are permitted. Thursday, December 2, 2010 - Beta 2 Tagging Trunk is frozen for beta release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. The usual beta rules apply as soon as the Beta tarballs have been generated. Wednesday, December 8, 2010 - Beta 2 Release The beta becomes available for general consumption. Monday, December 20, 2010 - Tagging Freeze for Release Candidate 1 During tagging freeze only compilation fixes for all platforms are allowed to be committed. Everything else (even showstopper fixes) *have* to be run through reviewboard, with the release-team and the affected maintainers as reviewer. Monday, December 20, 2010 - Hard API Freeze To allow the bindings people to have proper time to do there work in preparation to the final release, the API is now frozen. No more changes to APIs or header files (except docs) after this date, including older APIs and newly introduced libraries/APIs. Monday, December 20, 2010 - Hard Message Freeze Up to now you were able to do typo changes, but you had to mail kde-i18n-doc saying you made a typo fix change. From this moment on you need an explicit ok beforehand from kde-i18n-doc for every single string change. Monday, December 20, 2010 - Artwork and Bindings Freeze All artwork is frozen on this date. No new artwork should be added. Existing artwork can continue to be tweaked and fixed. No new additions to the language bindings, except optional bindings as permitting by the kde-bindings team. Tuesday, December 21, 2010 - Release Candidate 1 Tagging Trunk is frozen for release candidate tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. Wednesday, December 22, 2010 - Release Candidate 1 Release The release candidate is tagged from the branch. Only urgent fixes, such as those
Re: KDE SC 4.6 Schedule
A Dijous, 27 de maig de 2010, Tom Albers va escriure: On Wed, 26 May 2010 22:00:38 +0100, Albert Astals Cid aa...@kde.org wrote: I like it. Albert Thanks, I've put the schedule online now. Found a little error, Soft Message Freeze says Typo fixes can be fixed until Beta2, but Hard Message Freeze does not kick in until 12 days after Beta2, can we change the text of Soft Message Freeze to say Typo fixes can be fixed until Hard Message Freeze? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE SC 4.6 Schedule
A Diumenge, 30 de maig de 2010, Sebastian Kügler va escriure: On Sat May 29 2010 14:15:49 Albert Astals Cid wrote: Thanks, I've put the schedule online now. Found a little error, Soft Message Freeze says Typo fixes can be fixed until Beta2, but Hard Message Freeze does not kick in until 12 days after Beta2, can we change the text of Soft Message Freeze to say Typo fixes can be fixed until Hard Message Freeze? I'm not much of a translator (not at all, in fact), but aren't typos restricted to one language? And would the translated version still work (but be fuzzy)? If those assumptions are true (translations aren't broken by fixing a typo, but only marked as have another look), then I'd propose to just allow typo fixes, whenever. If not, please educate me :D fuzzy effectively means untranslated, so no your suggestion is not valid. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Mancala and KDE 4.5
A Dilluns, 31 de maig de 2010, Yuri Chornoivan va escriure: Hi! It seems kde-games-devel did not say yes or no to Mancala [1-3]. Does anybody know, will it be included in 4.5 or will it go to playground again? Thanks in advance. [1] http://lists.kde.org/?t=12728979253r=1w=2 [2] http://lists.kde.org/?l=kde-games-develm=127336767101378w=2 [3] http://lists.kde.org/?l=kde-games-develm=127481074527011w=2 Anyone from the release-team can answer this? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 4.4.5?
A Dilluns, 31 de maig de 2010, Anne-Marie Mahfouf va escriure: On Monday 31 May 2010 15:36:42 Allen Winter wrote: Do we want to make a 4.4.5 release? Seems like we could make a 4.4.5 in late June, since 4.5.0 is due early August. hmmm will we have any commits for it? Was 4.4.4 tagged already? I saw on websvn.kde.org.tags that it was... not sure how can one be aware of this, Reading the topic of #kde-devel? Reading the techbase page about schedules? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
