Thomas Pfeiffer ha scritto:
> On Montag, 12. Dezember 2016 07:39:24 CET Martin Gräßlin wrote:
>> Am 2016-12-11 22:35, schrieb Luigi Toscano:
>>> Hi,
>>>
>>> I would like to propose two changes to the Bugzilla workflow for our
>>> instance
>>> on bugs.kde.org. The two proposals are totally independe
Luigi Toscano ha scritto:
> On Monday, 12 December 2016 13:25:55 CET Boudewijn Rempt wrote:
>> On Mon, 12 Dec 2016, Martin Gräßlin wrote:
>>> No, that would affect more. For example when looking for a bug report I go
>>> to bugs.kde.org, Browse, kwin, component and then have a very small list
>>> o
On Montag, 12. Dezember 2016 07:39:24 CET Martin Gräßlin wrote:
> Am 2016-12-11 22:35, schrieb Luigi Toscano:
> > Hi,
> >
> > I would like to propose two changes to the Bugzilla workflow for our
> > instance
> > on bugs.kde.org. The two proposals are totally independent from each
> > other.
> >
>
Hey folks :)
At the last board meeting we've been discussing about Akademy and how
we want it to be next year. We'd love to get your input on this.
Most notably we're looking into knowing what would you like to see
different in Akademy 2017, and hopefully to be able to count on you to
make these c
On Monday, 12 December 2016 18:13:57 CET Boudewijn Rempt wrote:
> On Mon, 12 Dec 2016, David Edmundson wrote:
> > In terms of bugzilla workflow, we need to indicate 3 possible states of
> >
> > who we are waiting on:
> > - needs bugzilla input from a developer (current unconfirmed)
> > - needs b
On Mon, 12 Dec 2016, David Edmundson wrote:
> In terms of bugzilla workflow, we need to indicate 3 possible states of
> who we are waiting on:
>
> - needs bugzilla input from a developer (current unconfirmed)
> - needs bugzilla input from the reporter (current needsinfo)
> - doesn't require an
On Sun, Dec 11, 2016 at 9:35 PM, Luigi Toscano
wrote:
> Hi,
>
> I would like to propose two changes to the Bugzilla workflow for our
> instance
> on bugs.kde.org. The two proposals are totally independent from each
> other.
>
> a) use the "needinfo" flag instead of the NEEDINFO status.
>
> This i
On Mon, 12 Dec 2016, Martin Gräßlin wrote:
> Overall from what I read in this thread so far about it, I'm quite against
> this change. For me the focus is on getting those bugs away as I know that we
> won't get the backtrace. Try asking Arch users for a backtrace...
Maybe RESOLVED/BACKTRACE woul
On Mon, 12 Dec 2016, Luigi Toscano wrote:
> You can ask to another person without adding explicitly to the bug. The flag
> is cleared after asking, so you don't have to go and check the list of
> pending
> NEEDINFO for answer if you miss the email.
> This may not be relevant for you. It is for
On Monday, 12 December 2016 13:54:44 CET Boudewijn Rempt wrote:
> On Mon, 12 Dec 2016, Luigi Toscano wrote:
> > You could intercept them by filtering the content of the X-Bugzilla-Flags:
> > header.
>
> Okay.
>
> > It may not bring immediate benefits for everyone, and of course some
> > people
>
On Mon, 12 Dec 2016, Luigi Toscano wrote:
> You could intercept them by filtering the content of the X-Bugzilla-Flags:
> header.
Okay.
> It may not bring immediate benefits for everyone, and of course some people
> would not benefit from it, but if there are no regressions I think it would
>
On Monday, 12 December 2016 12:49:32 CET Boudewijn Rempt wrote:
> On Mon, 12 Dec 2016, Luigi Toscano wrote:
> > On Monday, 12 December 2016 10:22:37 CET Boudewijn Rempt wrote:
> > > On Sun, 11 Dec 2016, Luigi Toscano wrote:
> > > > Hi,
> > > >
> > > > I would like to propose two changes to the Bug
On Monday, 12 December 2016 13:25:55 CET Boudewijn Rempt wrote:
> On Mon, 12 Dec 2016, Martin Gräßlin wrote:
> > No, that would affect more. For example when looking for a bug report I go
> > to bugs.kde.org, Browse, kwin, component and then have a very small list
> > of the bugs for that component
On Mon, 12 Dec 2016, Martin Gräßlin wrote:
> No, that would affect more. For example when looking for a bug report I go to
> bugs.kde.org, Browse, kwin, component and then have a very small list of the
> bugs for that component and can find the bug report.
>
> If all the nonsentical needsinfo bug
On Mon, 12 Dec 2016, Luigi Toscano wrote:
> On Monday, 12 December 2016 10:22:37 CET Boudewijn Rempt wrote:
> > On Sun, 11 Dec 2016, Luigi Toscano wrote:
> > > Hi,
> > >
> > > I would like to propose two changes to the Bugzilla workflow for our
> > > instance on bugs.kde.org. The two proposals ar
Am 2016-12-12 11:55, schrieb Luigi Toscano:
On Monday, 12 December 2016 03:51:31 CET Nicolás Alvarez wrote:
> El 12 dic 2016, a las 03:39, Martin Gräßlin escribió:
>
> Am 2016-12-11 22:35, schrieb Luigi Toscano:
>> a) use the "needinfo" flag instead of the NEEDINFO status.
>> This is implemente
On Monday, 12 December 2016 10:22:37 CET Boudewijn Rempt wrote:
> On Sun, 11 Dec 2016, Luigi Toscano wrote:
> > Hi,
> >
> > I would like to propose two changes to the Bugzilla workflow for our
> > instance on bugs.kde.org. The two proposals are totally independent from
> > each other.
> >
> > a)
On Monday, 12 December 2016 03:51:31 CET Nicolás Alvarez wrote:
> > El 12 dic 2016, a las 03:39, Martin Gräßlin escribió:
> >
> > Am 2016-12-11 22:35, schrieb Luigi Toscano:
> >> a) use the "needinfo" flag instead of the NEEDINFO status.
> >> This is implemented on various instances of bugzilla (
On Monday, 12 December 2016 19:34:55 CET Eike Hein wrote:
> On 12/12/2016 07:27 PM, Elvis Angelaccio wrote:
> > On Sun, Dec 11, 2016 at 10:35 PM, Luigi Toscano
> >
> > wrote:
> >> I would introduce an ASSIGNED state so that developers that want to mark
> >> that they have acknowledged it and they
On 12/12/2016 07:27 PM, Elvis Angelaccio wrote:
> On Sun, Dec 11, 2016 at 10:35 PM, Luigi Toscano
> wrote:
>> I would introduce an ASSIGNED state so that developers that want to mark that
>> they have acknowledged it and they are going to work on it can do it.
>
> Don't we already have the ASSI
On Sun, Dec 11, 2016 at 10:35 PM, Luigi Toscano
wrote:
> I would introduce an ASSIGNED state so that developers that want to mark that
> they have acknowledged it and they are going to work on it can do it.
Don't we already have the ASSIGNED state? I just checked and I can
select it from the left
On 12/12/2016 06:35 AM, Luigi Toscano wrote:
> b) change back the initial state from UNCONFIRMED to NEW.
>
> This was the default until Bugzilla 3. But Many of our developers don't really
> use the UNCONFIRMED->CONFIRMED transition and this confuses the users.
> Moreover, NEW is still the initia
On Sun, 11 Dec 2016, Luigi Toscano wrote:
> Hi,
>
> I would like to propose two changes to the Bugzilla workflow for our instance
> on bugs.kde.org. The two proposals are totally independent from each other.
>
> a) use the "needinfo" flag instead of the NEEDINFO status.
I wouldn't like that. I'
23 matches
Mail list logo
