Re: Possible 4.3.0 blocker in the Konsole KPart?
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. 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
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
Re: Possible 4.3.0 blocker in the Konsole KPart?
Dirk Mueller wrote: We're too late in the process to wait for this for 4.3.0. Hopefully it gets solved for 4.3.1. I'm very sorry. That's ok, the consensus seems to be that it's not a blocker. We'll just have to make sure it's fixed in time for 4.3.1; I'll look into that now that my main dev box is back to working order (the last few days a broken graphics card made it less than useful - great timing as usual). Greetings, Dirk -- Regards, Eike Hein, h...@kde.org ___ 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 Tuesday 04 of August 2009 11:14:20 Aaron J. Seigo wrote: On Tuesday 04 August 2009, John Tapsell wrote: We still get lots of flack for the complete mess we made of 4.0 etc. i won't even argue the basis of your statement, but i will say that regardless of what anyone thinks about 4.0 it should not create subsequent paralysis and start us down a path of second-guessing and changing from the accepted release regimen. A high visibility bug like this will cause us even more grief. it's not high visibility. it's one odd visual artifact in konsole kpart usage when right clicking, and then only when you can see the top of the scroll area. it's not great, but it's hardly high visibility or of the sort that will cause us even more grief. A delay of a couple of days, on the other, people will understand. if we delayed for every bug of this magnitude, we'd never release [snip] Indeed, but unfortunately it as well sheds some light on amount of bugs actually introduced during development, and from downstream point of view it makes all 4.x.0 releases to be treated like development releases. Partially it's because KDE developers seem to be overloaded with amount of work - 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). It gives a little bit of feel of being half-baked, and really makes in 'distro ready' with 3rd or 4th patch release, but I guess it's supposed to be like this? Fortunately, every next minor release is in general less problematic than previous one, so there is some quality-wise improvement. -- 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
Re: Possible 4.3.0 blocker in the Konsole KPart?
Maciej Mrozowski wrote: Partially it's because KDE developers seem to be overloaded with amount of work - 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). Do note that in this case there's (still) no fix available - not on trunk either. If, at the time I spoke up, there had been a fix on trunk or on the branch, it's likely we'd have still gotten it into the tarball. -- Regards, Eike Hein, h...@kde.org ___ 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 Tuesday 04 August 2009, Maciej Mrozowski wrote: Indeed, but unfortunately it as well sheds some light on amount of bugs actually introduced during development, and from downstream point of view it makes all 4.x.0 releases to be treated like development releases. that's fine; if that's the case then ship 4.x.[1234] releases in stable and keep 4.x.0 in unstable or testing. packagers don't need to push every single release into their production line. Partially it's because KDE developers seem to be overloaded with amount of work when has that not been the case? shall we look at KDE3 releases to remind ourselves of this? ;) there are still unresolved crashes in kicker, btw. what makes it more difficult right now compared to latter KDE3 is that there's a lot of _new_ code. but really, it's something of a perennial issue. - 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. but i don't think that's what we're dealing with here, though, as Eike hints at in his email. -- 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 03.08.09 02:32:50, Eike Hein wrote: Aaron J. Seigo wrote: it's not a data loss bug, just not a very pretty thing. it also only seems to affect the top-left of the scrolled viewport. this is something that would be very good to fix in 4.3.1 for sure, but i don't think it's a release blocker? Dunno, that's what I'm wondering :). IMHO its not a release blocker, its not pretty but in most cases of embedding the kpart it'll only cause a broken display of the prompt. It also means the Scrollback sub-menu has disappeared from the context menu, though, so it's also a feature regression. But it won't eat anyone's children, I guess. You may call it a feature regression, the author of konsole might call it a conscious decision. Looking at the context menu of the kpart and the real app, they are having the same options. So I guess this might have been done on purpose. Andreas -- You are as I am with You. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Possible 4.3.0 blocker in the Konsole KPart?
Hi, this one seems to be fairly serious: https://bugs.kde.org/show_bug.cgi?id=186745 Basically, when you open the context menu in the Konsole KPart, most of the time you'll end up with the string No text overlayed over the ter- minal in the top-left corner. Also, the context menu has regressed vs. 4.2.x, removing several items - I think the two are probably one and the same bug, some sort of XMLGUI merge problem. Essentially, it's a highly noticable visual glitch and a functional regression. -- Regards, Eike Hein, h...@kde.org ___ 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 Sunday 02 August 2009 20:01:01 you wrote: On Sunday 02 August 2009, Eike Hein wrote: Hi, this one seems to be fairly serious: https://bugs.kde.org/show_bug.cgi?id=186745 it's not a data loss bug, just not a very pretty thing. it also only seems to affect the top-left of the scrolled viewport. this is something that would be very good to fix in 4.3.1 for sure, but i don't think it's a release blocker? I'm not sure I would call it a *blocker* either, but this is *the* terminal application we're talking about. The effect is also prominent in Yakuake so it probably affects all users of KonsolePart. Regards, - Michael Pyne 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?
Aaron J. Seigo wrote: it's not a data loss bug, just not a very pretty thing. it also only seems to affect the top-left of the scrolled viewport. this is something that would be very good to fix in 4.3.1 for sure, but i don't think it's a release blocker? Dunno, that's what I'm wondering :). It also means the Scrollback sub-menu has disappeared from the context menu, though, so it's also a feature regression. But it won't eat anyone's children, I guess. -- Regards, Eike Hein, h...@kde.org ___ 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?
Michael Pyne wrote: I'm not sure I would call it a *blocker* either, but this is *the* terminal application we're talking about. The effect is also prominent in Yakuake so it probably affects all users of KonsolePart. It's actually specific to the KPart, so yeah, I'm going to drown in bug reports about it (I maintain Yakuake), and it also affects Dolphin, Kate, etc. Regards, - Michael Pyne -- Regards, Eike Hein, h...@kde.org ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
