Short update on these projects:
Today, the bot moved from a white list to a black list [1]. This means that
we enabled the new bug workflow on most of the Firefox-related components.
We have been working with most of the triage owner to remove the last
components from the blacklist.
In parallel,
Le 03/04/2019 à 11:12, Axel Hecht a écrit :
Am 02.04.19 um 19:24 schrieb Sylvestre Ledru:
Because I had a few discussions about task vs enhancement, a good way to
make the difference between the two use cases is: If I ever need help with
this bug, should it come from someone in Product or an
Am 02.04.19 um 19:24 schrieb Sylvestre Ledru:
Because I had a few discussions about task vs enhancement, a good way to
make the difference between the two use cases is: If I ever need help with
this bug, should it come from someone in Product or an EPM?
Can I ask for clarification? Is it
task
On 3/12/19 12:53 PM, Kohei Yoshino wrote:
The User Story field will be soon removed from the new bug page.
https://bugzilla.mozilla.org/show_bug.cgi?id=1525376
The User Story has been used to track which domains should be added to
the Disconnect lists for a huge pile of tracking protection
Hello,
Good news, the Bugzilla changes (bug type & regressed by) are now live.
The implementation of the defect/task/enhancement feature was requested
first 20 years ago (back in 1999 -
https://bugzilla.mozilla.org/show_bug.cgi?id=9412).
Because I had a few discussions about task vs
An update on the bug type and regression fields:
Because of Firefox 66 and the subsequent 66.0.1 pwn2own chemspill, we decided
to delay the deployment of the change. We are now ready to deploy the new bug
type and regressions/regressed-by fields to production Bugzilla later this week.
A
Due to unexpected circumstances, we couldn’t deploy and migrate the bug type
field this week. Will try again next week as soon as on Monday.
Thanks,
-Kohei
On 2019-03-26 8:05 p.m., Kohei Yoshino wrote:
An update on the bug type and regression fields:
Because of Firefox 66 and the subsequent
I am not worried about this potential problem.
It doesn't have to be perfect, some folks (release managers, qa, etc) will
check that the values are correctly set.
In parallel, you probably noticed that we have a bot (autonag) which
automatically set/update a bunch of values.
@Felipe: yeah, the
Hello
Yes, it will be the same as block/depend in term of notification.
Sylvestre
Le 12/03/2019 à 19:12, David Major a écrit :
Will setting the "regressed by" field send mail to the subscribers of
the earlier bug? This was a useful aspect of the blocks/depends field.
On Tue, Mar 12, 2019 at
On Tue, Mar 12, 2019 at 10:53 AM Kohei Yoshino
wrote:
> The User Story field will be soon removed from the new bug page.
> https://bugzilla.mozilla.org/show_bug.cgi?id=1525376
Without a replacement that would be unfortunate. People have been asking
for what Honza described for more than 20
I've looked at the UX spec and Sylvestre's announcement, and I have
some relevant experience here working on teams which have used the
"enhancement" value of the "severity" field with the intent of using
that information to monitor our rate of defect introduction.
That workflow has turned out to
Does performance work count as "enhancement" or "task"?
On one hand, it's not strictly refactoring.. On the other hand, it is not
development of a new feature, per the proposed description of enhancement.
On Tue, Mar 12, 2019 at 3:20 PM Onno Ekker wrote:
> On 12/03/2019 18:59, Sylvestre Ledru
On 12/03/2019 18:59, Sylvestre Ledru wrote:
> Le 12/03/2019 à 17:48, Andrew McCreight a écrit :
>>
>> Secondly, to bikeshed a little, could there be some name besides
>> "task" for
>> that third category? Like I said above, everything we work as
>> developers is
>> a developer task. "Refactor"
Will setting the "regressed by" field send mail to the subscribers of
the earlier bug? This was a useful aspect of the blocks/depends field.
On Tue, Mar 12, 2019 at 1:59 PM Sylvestre Ledru wrote:
>
> Le 12/03/2019 à 17:48, Andrew McCreight a écrit :
> > On Tue, Mar 12, 2019 at 3:55 AM Sylvestre
Le 12/03/2019 à 17:48, Andrew McCreight a écrit :
On Tue, Mar 12, 2019 at 3:55 AM Sylvestre Ledru
wrote:
With this change, we are going to extend Bugzilla to add a new field with
three new values:
-
Defect - an issue in one of our products
-
Enhancement - a new feature or
One of the things that I have liked about Bugzilla is the lack of needing
to set something as a "bug" or an "enhancement". It seems this bug vs.
feature debate wastes unnecessary time. I have always liked thinking that
if Firefox is missing some feature, that in of itself is a bug. To me, it
keeps
The User Story field will be soon removed from the new bug page.
https://bugzilla.mozilla.org/show_bug.cgi?id=1525376
-Kohei
On 2019-03-12 1:47 p.m., Daniel Veditz wrote:
The "User Story" field can be (ab?)used for all those things. If the bug is
not an "enhancement" it's likely blank and just
Yes! You can use “type” like this:
https://bugzilla.allizom.org/buglist.cgi?quicksearch=type:defect
https://bugzilla.allizom.org/buglist.cgi?quicksearch=type:enhancement
https://bugzilla.allizom.org/buglist.cgi?quicksearch=type:task
And “regressed_by” and “regressions” should also work.
-Kohei
On Tue, Mar 12, 2019 at 4:50 AM Honza Bambas wrote:
> I wanted to suggest (but never done that) to have specific fields (text
> areas) in the bug form for following information:
> - explanation of the cause of the defect or rational for the bug
> - overview explanation of the fix for the defect
On Tue, Mar 12, 2019 at 3:55 AM Sylvestre Ledru
wrote:
> 2) Bug type - new field
> 3) Adding a new field called “Regressed by”
>
Will the new fields be searchable using quicksearch?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
On Tue, Mar 12, 2019 at 3:55 AM Sylvestre Ledru
wrote:
> With this change, we are going to extend Bugzilla to add a new field with
> three new values:
>
>-
>
>Defect - an issue in one of our products
>-
>
>Enhancement - a new feature or an improvement
>-
>
>Task - a
Damn you, reply-to field :) Sorry for spam everyone! Intended to
Sylvestre only.
-hb-
On 2019-03-12 12:50, Honza Bambas wrote:
Hi, replying privately, because I want to expose some crazy idea I had
a long time and this seems like a good opportunity.
I miss two things in bugzilla from the
Hi, replying privately, because I want to expose some crazy idea I had a
long time and this seems like a good opportunity.
I miss two things in bugzilla from the developer point of view:
- when I use it as a tool to look into the code's history (understand
changes made in the past)
- and be
Bugzilla is one of the key tools used for the development of Firefox since the
Netscape era. Even though this tool is serving us well, after interviewing a
bunch of people at every level inside the company, we realized that we need to
go the extra step.
Therefore, we decided to focus on
24 matches
Mail list logo
