Re: Intent to ship: -less RDM

[Mike Conley]

Thanks Micah, and everybody else who's been working on this! As someone
who's had to struggle at times with the special tunneling and frameloader
swapping that we do for the moziframe stuff for RDM, this is a very very
welcome change, and will allow us to get rid of some pretty confusing
front-end code. I've also heard from Fission / DOM folks that they'll be
happy when they can get rid of the mozbrowser iframe support altogether,
and this was the last consumer blocking its removal!

So great job and thanks again!

On Tue, 10 Mar 2020 at 14:29, Micah Tigley  wrote:

> Hi all,
>
> Later this week, we’ll be enabling a new version of the Responsive Design
> Mode tool that no longer relies on  as part of the
> initiative to make DevTools Fission-compatible. For now, the pref will only
> be enabled in Firefox Nightly as we work with QA to ensure the stability of
> the tool.
>
> This new version of RDM will be embedded inside the browser UI (rather
> than live in a tab like today) and website content will be rendered inside
> the  element just like normal. Users should not expect any
> significant difference between this version and the current one.
>
> Pref: devtools.responsive.browserUI.enabled
>
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1621306
>
> Tracking bug for RDM Fission:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1574885. We ask anyone
> finding anything wrong with the new tool once the pref is on to report bugs
> blocking this meta.
>
> - Micah
> ___
> firefox-dev mailing list
> firefox-...@mozilla.org
> https://mail.mozilla.org/listinfo/firefox-dev
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Land your tests for now-public security bugs

[j.j.]

Am Dienstag, 10. März 2020 16:05:07 UTC+1 schrieb Tom Ritter:
> [land-tests: 2020/04/05]

2020-05-04  ISO 8601 Date please!

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[dlawrence]

the following changes have been pushed to bugzilla.mozilla.org:

 

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200309.1)

 

https://bugzil.la/1619361 : Adjust Reps Application Form to new criteria

https://bugzil.la/1620452 : secbugs report should be update to allow
emailing to multiple addresses

https://bugzil.la/1619609 : Update /rest/whoami to return group membership,
and support authenticating with a Phabricator conduit token

https://bugzil.la/1620236 : Comments on submitted bugs are re-populated if
user chooses to show next bug in my list after changing a bug

https://bugzil.la/1605761 : It's not clear at all that you need to hit
-enter- to save a comment tag.

 

dkl

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Land your tests for now-public security bugs

[Tom Ritter]

On Monday, March 9, 2020 at 6:40:16 PM UTC-5, Cameron McCormack wrote:
> Can we have the bots that operate on Bugzilla needinfo bug assignees when a 
> bug is opened up and has an "in-testsuite?" flag?

I had been planning on making an autonag rule that reads a whiteboard tag like 
[land-tests: 2020/04/05] for ni-ing the assignee - that would avoid the need 
for the bug to be opened up.  Since the number of people doing sec-approval and 
needing to set the whiteboard tag in the correct format is very small, I think 
this would work better, but I'm open to suggestions.  (I'm also open to anyone 
beating me to the implementation!)

-tom
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

[IMPORTANT] Submit your PI Requests for Firefox 76 QA feature testing by Mar 13

[Tania Maity]

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx76. In order to help with the process,
please *submit your PI-Request
*
   by *Friday, March
13*. Please note that the Feature Technical Documentation

for *features require beta testing* needs to be ready before by March 20th.
This is needed to assure QA will be involved in your feature development
work for the 76 cycle. For *features that require Nightly testing*, please
provide documentation *as soon as possible*. QA cannot start working on
your feature without documentation. Along with these, please create
corresponding feature trello cards in Firefox
 board by March 20th.

Kindly ensure to update the *Priority of the PI request *(Highest, High,
Medium, Low, Lowest) as during feature prioritization process, this will be
factored in to ensure critical features have sufficient resources assigned.

*Q: What happens after the deadline?*
A: After the deadline QA will come back with a prioritized list of work
that represents what we are committing to for the next cycle. We want to
ensure this list matches eng and product expectations.

* Q: What if I miss the deadline?*
A: We reserve the right to say that we can't pick up work for late requests
in the current cycle. You can still develop and execute your own test plan
or defer the work to the following cycle.


* Q: What about unknown or unexpected requests? What if there is a business
reason for a late request?*
A: In order to remain flexible, we will keep some percentage of time open
for requests like these.

*Q: There's no way I'm going to remember to do this.*
A: Do it now! I'll also send out a reminder by the end of this week.

Thanks,
Tania
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform