Re: KDE 3.5.10
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 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.10
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? Regards, -- Benoit Minisini ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.10
On mardi 19 août 2008, Stephan Kulow wrote: 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. It's just that I didn't know the tagging date of KDE 3.5.10. Someone told me that it will be Aug. 20th, but that was just a guess. Apparently I missed the mail where you said it is today, so I was surprised. 3.5 branch is frozen since ages - I'm just packaging it for the fixes in the branch. I don't understand the last sentence: /branches/KDE/3.5 is not frozen, as many people put patches there yet, as I did with kicker. Anyway, all my patches were committed in time (except the last one, but it was not important), and I hope things were tested enough! Regards, -- Benoit Minisini ___ 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: KDE 3.5.10
Am Dienstag 19 August 2008 schrieb Albert Astals Cid: 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. If that are the options, I go for reverting. Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.10
On Tuesday 19 August 2008 18:52:39 Benoit Minisini wrote: On mardi 19 août 2008, Stephan Kulow wrote: 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. It's just that I didn't know the tagging date of KDE 3.5.10. Someone told me that it will be Aug. 20th, but that was just a guess. Apparently I missed the mail where you said it is today, so I was surprised. 3.5 branch is frozen since ages - I'm just packaging it for the fixes in the branch. I don't understand the last sentence: /branches/KDE/3.5 is not frozen, as many people put patches there yet, as I did with kicker. feature-frozen. I'm not exactly happy with merging in things at this point, especially not the kicker patches you're talking about. Anyway, all my patches were committed in time (except the last one, but it was not important), and I hope things were tested enough! I don't think that a lot of people are compiling and testing the 3.5 branch, so adding in features and patches that change behaviour in a codebase as fragile as kicker doesn't sound like a smart thing to do to me. -- 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: KDE 3.5.10
On Tuesday 19 August 2008, Benoit Minisini wrote: So, having done all this work during a month just to hear that everything will be removed at the day of the release is a bit... rude. Benoit, I think the issue here is that people trying to decide what to do about it don't have the information necessary to make an informed decision. So they default to revert everything. A list of changes you made to kicker here would probably fix that. -- 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 Trolltech 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: KDE 3.5.10
On mardi 19 août 2008, Aaron J. Seigo wrote: On Tuesday 19 August 2008, Benoit Minisini wrote: So, having done all this work during a month just to hear that everything will be removed at the day of the release is a bit... rude. Benoit, I think the issue here is that people trying to decide what to do about it don't have the information necessary to make an informed decision. So they default to revert everything. A list of changes you made to kicker here would probably fix that. OK! I did this list for Danny Allen some days ago. He asked it me for the KDE digest. Here is this list, in arbitrary order. 1) Desktop names are drawn with a shadow, so that they are readable on a transparent background. 2) Applet handles now use a themed arrow button. They lost their unneeded big left margin too (only one pixel now). 3) The taskbar flickers less, especially on desktop changes. Some unneeded taskbar button repaints were removed. 4) The system tray arrow button now follows the widget theme. The useless vertical line was removed. The system tray layout algorithm was fixed too. 5) The weather applet button now behaves as other kicker buttons. 6) When moving a panel, the frame is now drawn with top-level unmanaged windows, using the title bar color. 7) The mixer applet now displays nicely on a transparent background. 8) The anti-aliased clock was fixed. Other little bugs were fixed in the clock applet too. 9) The runner applet layout algorithm was fixed. 10) The moon applet displays correctly on a transparent background. 11) The character table applet now follows transparency, and adapt the character font size to its cell size. 12) The eyes applet is anti-aliased now. 13) The little puzzle game better follows transparency. 14) The add applet dialog was fixed: no more unneeded space to its end, and you can drag drop any button from it. 15) When a panel has a background image that is colorized according to the global palette, its one-pixel border is colored the same way. 16) The background image is correctly mirrored for top panels. 17) Panels now work correctly when they have scroll buttons. These scroll buttons now use themed arrows. 18) Changing the widget theme makes kicker automatically restart. Otherwise, the layout of some applets may become incorrect. 19) The transparency of many applets was fixed. And now they use kicker buttons instead of normal or specific ones. 20) The background of applets and buttons is automatically refreshed when they are moved. 21) In transparent mode, applet handles are drawn with a transparent rectangle shadow, and not a themed dock bar anymore. I made two screenshots of these changes, that I sent to Danny. If anyone wants, I will send them to their private e-mail. I browsed bugs.kde.org too, and I put a comment fixed in KDE 3.5.10 in all fixed bugs (I didn't think that the patches would be reverted). Regards, -- Benoit Minisini ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.10
On Tuesday 19 August 2008, Benoit Minisini wrote: On mardi 19 août 2008, Aaron J. Seigo wrote: On Tuesday 19 August 2008, Benoit Minisini wrote: So, having done all this work during a month just to hear that everything will be removed at the day of the release is a bit... rude. Benoit, I think the issue here is that people trying to decide what to do about it don't have the information necessary to make an informed decision. So they default to revert everything. A list of changes you made to kicker here would probably fix that. OK! I did this list for Danny Allen some days ago. He asked it me for the KDE digest. Here is this list, in arbitrary order. personally i have no issues with the concepts in this list; but i haven't tested any of the changes or looked at the code that actually went into svn (though i did look over some patches sent to kde-devel@) so i can't comment further than assuming they are correctly implemented, they shouldn't be too dangerous for the branch. -- 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 Trolltech 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
Putting Playground in some order
Hi,
should we get some more structure into Playground? I fear it will otherwise
end in the state kdenonbeta has been before if it isn't already: Lot's of
started projects, but most of them dead code, making people uninterested in
looking into it at all.
Take for example playground/utils:
http://websvn.kde.org/trunk/playground/utils/?sortby=date
There are currently 45 projects inside. 18 haven't seen any activity since
seven month and more, only 8 have seen activity in the last four month
besides scripty. There is also a mix of KDE 3 and KDE 4 dependencies.
So I would like to propose to have some little policy for playground:
a) Projects which have been without a commit for more than five month are
moved to
tags/unmaintained/playground/$submodule/{3,4}
if the authors/maintainers do not oppose within a month.
b) KDE3 based projects are moved to branches/playground/kde3/$submodule/ (cmp.
branches/extragear/kde3/$submodule)
By keeping only active projects in playground third-parties like translators,
dashboard maintainers or check drivers (cmp. *) do not spend their resources
on dead things. And splitting of the KDE3 based ones should have been done
long time ago.
*
http://englishbreakfastnetwork.org/krazy2/index.php?component=playgroundmodule=utils
Then the toplevel structure of trunk/playground does not exactly reflect the
current KDE modules:
accessibility/
artwork/
base/
bindings/
devtools/
edu/
games/
graphics/
ioslaves/
multimedia/
network/
office/
pim/
sysadmin/
utils/
While trunk/KDE consists of:
kde-common/
kdeaccessibility/
kdeadmin/
kdeartwork/
kdebase/
kdebindings/
kdeedu/
kdegames/
kdegraphics/
kdelibs/
kdemultimedia/
kdenetwork/
kdepim/
kdesdk/
kdetoys/
kdeutils/
kdevelop/
kdewebdev/
Extragear is not matched exactly, too:
base/
graphics/
libs/
multimedia/
network/
pim/
plasma/
sdk/
security/
utils/
Is this intended, or should the submodules be restructured to match the main
KDE modules? Matching the main modules would make it straigthforward to have
the module coordinator also care for the corresponding playground submodule.
Perhaps extragear structure should be aligned to the main modules, too?
Because projects in playground could rather end there.
Motivation:
I want to give the projects in playground/utils some more visibilty by adding
them to utils.kde.org, e.g. to show useful overviews of development status,
similar to
http://utils.kde.org/projects/kwalletmanager/development.php
So people are aware what is happening and do not continue to do things like
implementing three power manager applets independently, like currently
happening.
But this would mean binding of playground/utils to kdeutils. I am not sure if
this is a good idea.
Comments, please?
Friedrich
--
Okteta - KDE Hex Editor, coming to you with KDE 4.1
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
Re: Putting Playground in some order
On Tuesday 19 August 2008 17:58:29 Friedrich W. H. Kossebau wrote: Hi, should we get some more structure into Playground? I fear it will otherwise end in the state kdenonbeta has been before if it isn't already: Lot's of started projects, but most of them dead code, making people uninterested in looking into it at all. I agree we should cleanup every now and then -- certainly the dead stuff should be removed. And I agree that kde3 apps should be moved into a substructure. Keeping mostly the same top-level structure is also a good idea. Doesn't have to be exactly the same as trunk/KDE. However, I don't want to give too much formality to playground. We want people to feel free to explore ideas and stuff. In summary: - how about an widely disseminated email asking people to remove dead code and to move their kde3 stuff into playground/$module/kde3 I'm not so sure that we should be moving old playground code into unmaintained. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
