Robert Kaiser wrote:
*Ideas for what products we should remove*
And how the XXX should users of those products file new bugs then?
we're talking about removing products from the list of products
initially shown to users, not about removing the products from bmo
completely.
the complete list
Steve Fink wrote:
The name target milestone implies an aspirational landing. Should we
just change the bug template to change the name of the field?
that would be difficult as other projects which use bugzilla.mozilla.org
use the target milestone field as a .. target milestone ;)
while it
howdy,
we'd like to extend bugzilla.mozilla.org to log which channel the
reporter's version of firefox is using; however i can't figure out if
this information is available to javascript.
i initially thought about using browser/config/version/version.txt based
on the version in the
wow, looks like is missed quite a lot while my power was out..
a high level response from the bmo team is: a goal for this quarter is
to address a lot of the review related issues.
i've been working through splinter issues and fixing the easy ones (it
no longer has problems with
being touched in the diff. this
is being worked on by mhoye (bug 774145).
thanks!
--
byron jones - :glob - bugzilla.mozilla.org team -
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
.
--
byron jones - :glob - bugzilla.mozilla.org team -
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
thanks to dylan's work on bug 489028, bugzilla now tracks when you view
a bug, allowing you to search for bugs which have been updated since you
last visited them.
see my blog post for more details: http://wp.me/p1JUqW-9M
--
byron jones - :glob - bugzilla.mozilla.org team
screenshot from.
--
byron jones - :glob - bugzilla.mozilla.org team -
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
are watching? set up a filter!
or perhaps you only want to be informed about qa related changes on bug
where you are the assignee? set up a filter!
see
http://globau.wordpress.com/2014/07/10/using-bugmail-filtering-to-exclude-notifications-you-dont-want/
for more details.
--
byron jones - :glob
, except for a few components I care about
more...
no, watching is your relationship with the bug, not a specific component.
--
byron jones - :glob - bugzilla.mozilla.org team -
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https
created (existing
filters won't be impacted).
--
byron jones - :glob - bugzilla.mozilla.org team -
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Philipp Kewisch wrote:
On 7/14/14 8:13 AM, Byron Jones wrote:
Now, I got a notification for bug 1038029 where Magnus added himself as
CC and also added the regression keyword. No comment was added. Does
it take some time until the filters are applied? Shouldn't the bugmail
filter have filtered
L. David Baron wrote:
On Monday 2014-07-14 21:50 +0800, Byron Jones wrote:
Ehsan Akhgari wrote:
2. Can we get a field designating the creation of bugs, so that I
can set things up so that I get bugmails for new bugs no matter
what?
one already exists, but i forgot to change the visible
Ehsan Akhgari wrote:
On 2014-07-14, 9:50 AM, Byron Jones wrote:
Ehsan Akhgari wrote:
1. Can we get a Any direct relationship field in the Relationship
drop-down which means Assignee || Reporter || QA Contact || CC'ed ||
Mentoring (basically all cases except Watching)?
how is that different
yes, that's how it should behave.
- Original Message -
From: Gavin Sharp ga...@gavinsharp.com
To: Byron Jones g...@mozilla.com
Cc: dev-platform dev-platform@lists.mozilla.org
Sent: Saturday, 19 July, 2014 3:54:37 AM
Subject: Re: fine-grained filtering of bugmail
I added the following
when viewing untriaged bugs,
which sets the platform to the reporter's
--
byron jones - :glob - bugzilla.mozilla.org team lead -
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
products will still
be able to default to all/all should the owners desire that).
-glob
--
byron jones - :glob - bugzilla.mozilla.org team lead -
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
love).
https://www.bugzilla.org/docs/4.2/en/html/query.html#individual-buglists
(section 5.5.5).
-glob
--
byron jones - :glob - bugzilla.mozilla.org team lead -
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org
Byron Jones wrote:
this feature exists and is called bug tagging.
you'll need to enable it via the prefs page (it's disabled by default
because the ux needs some love).
https://www.bugzilla.org/docs/4.2/en/html/query.html#individual-buglists
(section 5.5.5).
i should add that the plan
the first aurora build.
I apologize for the very late notice. Of course, we will be friendly
with uplift requests.
please update https://wiki.mozilla.org/RapidRelease/Calendar and the
associated ICS files.
thanks.
--
byron jones - :glob - bugzilla.mozilla.org team lead
Richard Z wrote:
tried dxr as replacement for lxr yesterday and today and it
does not seem to work for me.
Whatever I type into the searchbox the results is just an
empty "This page was generated by DXR ."?
https://dxr.mozilla.org/mozilla-central/search?q=voice=true
Displaying source like
Jörg Knobloch wrote:
Some more feedback: While "3 years ago" is nice for the date display,
I'd also like to see the full date and hour in a copyable form. Another
bug for that? Or is there a setting that will do it already?
set "Use absolute format instead of relative time when viewing a bug"
David Burns wrote:
We should try mitigate the security problem and fix our nit problem
instead of bashing that we can't handle re-reviews because of nits.
one way tooling could help here is to allow the reviewer to make minor
changes to the patch before it lands.
ie. "r+, fix typo in comment
yes -
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch
covers this.
please read all of the document linked by cameron and this one.
-glob
Enrico Weigelt, metux IT consult wrote:
On 31.07.2017 09:23, Cameron McCormack wrote:
Hi Enrico,
Firefox patches
To answer the other part of your question, MozReview will be disabled for
active use across the board, but it is currently used by a small number of
projects. Splinter will be disabled on a per-product basis, as there may be
some projects that can't, won't, or shouldn't be migrated to
Yeah, I live in the assumption that bugzilla bugs will contain all the
review information also
in phabricator era.
i believe the current plan is to mirror just the outcome of the review
to bugzilla (ie. that a review exists, and set the review flag).
if comments should be mirrored to bugzilla
Milan Sreckovic wrote:
One thing that hasn't been explicitly mentioned, and I hope switching to
phabricator would fix it (though it does sounds like an orthogonal
issue) - the patches that are attached to bugzilla are often not the
ones that actually landed, because last minute changes were made
Consider that we are talking about "turning off" mozreview now. Will all
the bugzilla links to those reviews go dead? Or do we have to maintain a
second service in read-only mode forever?
the patches will be archived in some form.
how this looks is yet to be fully fleshed out - ideas
TOTP does not require a smartphone.
there's software TOTP clients that can be run on your desktop, and i'm
also seeing TOTP support baked into some password managers. that
clearly isn't as secure as the second factor implemented on a second
device, however desktop TOTP does provide better
Axel Hecht wrote:
One thing I'm missing is the ability to do mono-repo imports. Say we
want to vendor in
https://github.com/projectfluent/fluent.js/tree/master/fluent-gecko.
i'm not sure i understand the specific concerns around mono-repos; you
can use exclude/include to perform a selective
Mark Banner wrote:
There are some directories where we only import a file from a
third-party and it is alongside other files in that same directory, e.g.
testing/modules has "ajv-4.1.1.js" and "sinon-2.3.2.js" imported from
elsewhere.
How do they fit into this scheme?
they would have to be
glob wrote:
The plan is to create a YAML file for each library containing metadata
such as the homepage url, vendored version, bugzilla component, etc. See
https://goo.gl/QZyz4xfor the full specification.
this should be: https://goo.gl/QZyz4x for the full specification.
--
glob —
this should be: https://goo.gl/QZyz4x for the full specification.
This format is essentially assuming the vendored code comes from a VCS
repository. We have plenty of third party code that is imported through
upstream tarballs, so this should probably be accounted for.
we can certainly
this should be: https://goo.gl/QZyz4x for the full specification.
This format is essentially assuming the vendored code comes from a VCS
repository. We have plenty of third party code that is imported through
upstream tarballs, so this should probably be accounted for.
we can certainly
34 matches
Mail list logo
