Christoph Cullmann wrote:
> I think one of the problems with our current Bugzilla database is that it
> contains a lot of "old" bugs and wishs.
>
> As the manpower is limited and we sometimes not even keep up with the
> incoming new bugs, might it be a good idea to adopt a similar strategy
> like
On Friday, July 31, 2015 09:55:30 PM Thomas Lübking wrote:
> On Freitag, 31. Juli 2015 19:29:53 CEST, Ingo Klöcker wrote:
> > I also do not see the point in nagging the user after a certain period of
> > time if nobody else ever cared to comment on the bug. Feels a bit like
> > little kids asking "
On Freitag, 31. Juli 2015 19:29:53 CEST, Ingo Klöcker wrote:
I also do not see the point in nagging the user after a certain period of
time if nobody else ever cared to comment on the bug. Feels a bit like
little kids asking "Are we there yet?" over and over again.
The idea is not only to get
On Wednesday, July 29, 2015 11:03:15 AM Martin Klapetek wrote:
> On Wed, Jul 29, 2015 at 11:47 AM, Marc Mutz wrote:
> > On Wednesday 29 July 2015 09:04:42 Martin Klapetek wrote:
> > > Can you perhaps create a single diff against 5.5/dev/master
> > > which could be easily applied? That should make
On Wednesday 29 July 2015 09:04:42 Martin Klapetek wrote:
> Can you perhaps create a single diff against 5.5/dev/master
> which could be easily applied? That should make things
> much easier to help :)
Assuming you're talking about the dbus changes, wouldn't you actually want to
cherry-pick them
GENERAL INFO
BUILD UNSTABLE
Build URL:
https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/10/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Wed, 29 Jul 2015 10:00:38 +
Build duration: 44 min
CHANGE SET
Revision 085d7d74c9d9d4e31442e411038fcf484083da1
On Friday, July 31, 2015 07:29:53 PM Ingo Klöcker wrote:
> On Friday 31 July 2015 12:00:22 Allen Winter wrote:
> > On Friday, July 31, 2015 04:01:37 PM Thomas Lübking wrote:
> > > On Freitag, 31. Juli 2015 14:05:09 CEST, laurent Montel wrote:
> > > >> Especially for KDE PIM, given the size of the u
On Friday 31 July 2015 12:00:22 Allen Winter wrote:
> On Friday, July 31, 2015 04:01:37 PM Thomas Lübking wrote:
> > On Freitag, 31. Juli 2015 14:05:09 CEST, laurent Montel wrote:
> > >> Especially for KDE PIM, given the size of the userbase and the amount
> > >> of
> > >> developers (3), bugs ofte
On Friday, July 31, 2015 04:01:37 PM Thomas Lübking wrote:
> On Freitag, 31. Juli 2015 14:05:09 CEST, laurent Montel wrote:
>
> >> Especially for KDE PIM, given the size of the userbase and the amount of
> >> developers (3), bugs often take more than a year to get to and
> >> to be fixed.
> >
> >
On Freitag, 31. Juli 2015 14:05:09 CEST, laurent Montel wrote:
Especially for KDE PIM, given the size of the userbase and the amount of
developers (3), bugs often take more than a year to get to and
to be fixed.
+1
As Daniel wrote we have a lot of bug and a very small team.
So we can't able t
El Dilluns, 18 de maig de 2015, a les 13:38:36, Albert Astals Cid va escriure:
> El Dilluns, 18 de maig de 2015, a les 08:00:07, Martin Koller va escriure:
> > On Sunday 10 May 2015 19:39:07 Alex Merry wrote:
> > > On Saturday 09 May 2015 22:54:49 Martin Koller wrote:
> > > > I'm working on porting
Le Friday 31 July 2015, 11:07:54 Daniel Vrátil a écrit :
> On Friday, July 31, 2015 10:12:00 AM Christoph Cullmann wrote:
> > Hi,
> >
> > I think one of the problems with our current Bugzilla database is that it
> > contains a lot of "old" bugs and wishs.
>
> True that!
>
> > As the manpower is
On Fri, Jul 31, 2015 at 9:48 PM, Martin Klapetek
wrote:
> One thing that bothers me a bit is the commits shas having format like
> rKONVERSATIONc64d1cd32445f6921109fdbdb17ae44378d404c5
>
> Can something be done about the rPROJECTNAME prefix? I find it
> quite confusing and hard to read; if you're
One thing that bothers me a bit is the commits shas having format like
rKONVERSATIONc64d1cd32445f6921109fdbdb17ae44378d404c5
Can something be done about the rPROJECTNAME prefix? I find it
quite confusing and hard to read; if you're looking at commits in
a specific repo, I think it's clear to which
On Fri, Jul 31, 2015 at 8:42 AM, Kevin Kofler wrote:
> Luigi Toscano wrote:
>> Feedback on Phabricator gathered outside the BoF from people who could not
>> attend:
>
> Were there no complaints about the fact that you can still not view anything
> at all without logging in?
This has now been corr
El Divendres, 31 de juliol de 2015, a les 11:02:44, Dominik Haumann va
escriure:
> Hi,
>
> On Fri, Jul 31, 2015 at 10:12 AM, Christoph Cullmann
>
> wrote:
> > Hi,
> >
> > I think one of the problems with our current Bugzilla database is that it
> > contains a lot of "old" bugs and wishs.
> >
On Fri, Jul 31, 2015 at 11:02 AM, Dominik Haumann wrote:
>
> Of course, some wishes and valid bugs would be automatically closed then,
> too.
> But this is probably not a big issue, since a wish that will never get
> implemented
> is useful neither for us as developers nor for the users at all.
>
On Friday, July 31, 2015 11:02:44 AM Dominik Haumann wrote:
> Comments? Strong objections? ;)
+1 - I think it's a sensible strategy and something we kind of implemented
with introducing a new product for Plasma: thus getting rid of the old cruft.
Fun note: I set a bug as RESOLVED FIXED yesterda
On Friday, July 31, 2015 10:12:00 AM Christoph Cullmann wrote:
> Hi,
>
> I think one of the problems with our current Bugzilla database is that it
> contains a lot of "old" bugs and wishs.
True that!
>
> As the manpower is limited and we sometimes not even keep up with the
> incoming new bugs,
Hi,
On Fri, Jul 31, 2015 at 10:12 AM, Christoph Cullmann
wrote:
> Hi,
>
> I think one of the problems with our current Bugzilla database is that it
> contains a lot of "old" bugs and wishs.
>
> As the manpower is limited and we sometimes not even keep up with the
> incoming new bugs, might
> it
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121755/#review83215
---
Ship it!
the description makes a good commit message, so plea
Hi,
I think one of the problems with our current Bugzilla database is that it
contains a lot of "old" bugs and wishs.
As the manpower is limited and we sometimes not even keep up with the incoming
new bugs, might
it be a good idea to adopt a similar strategy like the Qt Project and expire
bugs
22 matches
Mail list logo
