Re: KAdrresbook and KContactmanager
Am Donnerstag 06 August 2009 02:36:16 schrieb Allen Winter: > On Wednesday 05 August 2009 5:39:22 pm you wrote: > > 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. > > No need to battle. > > I suck. I'm saw the change was happening early this morning but I didn't > have the chance to properly coordinate. I take full blame. > > Regarding the bugs: the kaddressbook maintainer basically said > he isn't fixing any bugs in the old kaddressbook anymore and that's > why he killed all the bugs there and started over. Of course, bugs > from the 4.3 kaddressbook can go into the fresh product, but I > have no idea how much effort will go toward fixing them. > > Apologies again. I await my punishment. > Ok here it is: Write a documentation for the new kaddressbook ;-) -- Burkhard Lück ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KAdrresbook and KContactmanager
On Wednesday 05 August 2009 5:39:22 pm you wrote: > 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. > No need to battle. I suck. I'm saw the change was happening early this morning but I didn't have the chance to properly coordinate. I take full blame. Regarding the bugs: the kaddressbook maintainer basically said he isn't fixing any bugs in the old kaddressbook anymore and that's why he killed all the bugs there and started over. Of course, bugs from the 4.3 kaddressbook can go into the fresh product, but I have no idea how much effort will go toward fixing them. Apologies again. I await my punishment. -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KAdrresbook and KContactmanager
On Wednesday 05 August 2009 23:39:22 Albert Astals Cid wrote: > 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? Yeah, but in practice it'll boil down to Allen reading it here, and then passing your advice on to the kde-pim list anyway. I think the problem was mainly caused by unawareness of what works best for the docs team, and that a quick email with "we've moved this to that place" would make your life a lot easier -- which is something we all want :) As to the "Don't we accept bugs for kaddressbook in 4.3" is indeed an issue. We've had similar situations for other stuff as well, by the way. I'll have to read up on kde-pim to get a good idea of the details of replacing kaddressbook with kcontactmanager (and then renaming it), so I can't really tell what would be the best solution. > 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. Don't worry, PIM people are nice people :) -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 signature.asc Description: This is a digitally signed message part. ___ 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
Re: KAdrresbook and KContactmanager
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) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software signature.asc Description: This is a digitally signed message part. ___ 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?
On Wednesday 05 of August 2009 08:17:03 John Tapsell wrote: > Agreed. I can't get the hang of svn backporting, and so I simply never do > it. I'm a bit scared hearing this.. Maybe because being packager I usually rely on developers to decide about the way product is supposed to look like (not to mention it's far easier this way...) - and if backporting was not popular among developers (fortunately it's usually not the case), then trunk would always feel "broken" (hey, it's supposed to be that way :) - and stable branch would be underdeveloped/abandoned/forgotten - this way users would never really get polished release. That being said I really think that migrating to better SCM is crucial and should be done as soon as possible. Aaron mentioned possibility of working in stable and then forward porting. While it may certainly bring more focus on bugfixes, it may cause features being introduced at smaller pace - it's up to you to decide what's most appropriate at this point of KDE release timeframe. In any way - like Aaron noted, SVN doesn't help here (unless you forget about branches and go back to continuous in-trunk development - but that would expose patch releases to regressions so it's dead end). > Once we have git, I'd like to see this issue revisited. I would > prefer that KDE got a reputation of "releases when ready". Just start > skipping the release that we currently call ".0". That won't solve anything. x.y.0 releases are important - even just for their PR value - even if they're half-baked - it's just up to distributions to pick the one that satisfies it best. Reputation of high quality can be achieved without skipping releases. It "just" needs: - regarding developers - the will to write reliable, bullet-proof code and backport it if needed - for developers - tools that help and don't disturb (currently lack of thereof can be only compensated by even greater developers' will) - better distro<->developers cooperation, distributions provide free testers after all (btw, how many of you use stable branch daily?) Are there currently any serious problems with such cooperation? -- regards MM signature.asc Description: This is a digitally signed message part. ___ 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: 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 : > >> - 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
