Re: Closure of #ateam irc channel

[glob]

David Burns wrote on 22/1/19 5:16 pm:


 *

#engworkflow - Engineering Work flow: Tooling for engineers
phabricator, lando.

#engworkflow isn't the best channel for most phabricator/lando 
questions; instead please ask questions in their respective channels:  
#phabricator and #lando.


--
glob — engineering workflow — moz://a

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

Re: [IMPORTANT] QA Firefox 67 feature testing pi-requests deadline is January 23

[Tom Grabowski]

Hi,

Just a reminder that the deadline for Fx67 PI Requests is tomorrow, January
23.
If you have not done it yet, please send your requests now.

Regards,
Tom


On Thu, Jan 17, 2019 at 1:15 PM Tom Grabowski 
wrote:

> Hi,
>
> Similar to what QA did for previous Firefox feature testing prioritization
> ,
> we would like to do the same for Fx67. In order to help with the process, 
> *please
> submit your pi-request
>  by January 23. *This
> is needed to assure QA will be involved in your feature development work
> for the Nightly 67 cycle.
>
>
> *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? What do we do with experiments and System
> Add-ons?*
> 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 next week.
>
> Thanks,
> Tom
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: How do we land `./mach vendor rust` patches, these days?

[Bobby Holley]

It's worth noting that pulling in code from crates.io has different trust
properties than NSS. In general, it's the developer and reviewer's
responsibility to ensure that any newly-vendored Rust code is not
malicious. This usually doesn't necessitate a painstaking line-by-line
review, but needs something more than "rs=me on whatever gets pulled in
when you cargo update".

If Phabricator is choking on large diffs, that seems like a very
high-priority bug for the Engineering Workflow team to fix, so you should
file a bug if you haven't already. In the mean time, phlay might work.

On Sun, Jan 20, 2019 at 7:47 PM Martin Thomson  wrote:

> On Sat, Jan 19, 2019 at 7:42 AM Emilio Cobos Álvarez 
> wrote:
>
> > For others (assuming you're hitting the max_post_size limit) I think
> > you're out of luck and need to submit them via splinter[2].
> >
>
> When vendoring NSS, which we do often, we've sometimes resorted to asking
> for review for a script, or one-line command.  As long as that identifies
> the thing that is being vendored precisely, then you can go and review the
> changes based on the command.
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Closure of #ateam irc channel

[David Burns]

For the last 2 years the Automation and Tools team (#ateam) has not existed
as a single function as parts of the team were split up between Firefox
Engineer Operations and Product Integrity.

As traffic in #ateam has dropped it is time to close this irc channel and
request people go to more specific channels to get the help that you need.


   -

   #build - Build team: Compilation of Firefox
   -

   #vcs - hg.mozilla.org
   -

   #engworkflow - Engineering Work flow: Tooling for engineers phabricator,
   lando.
   -

   #bmo - bugzilla.mozilla.org
   -

   #Sheriffs - Sheriffing team: Sheriffing of trees
   -

   #cia - CI and Automation team: Test harnesses and CI scheduling
   -

   #treeherder - Treeherder team: Treeherder specific problems or queries
   -

   #perftest - Performance Testing: Performance test harnesses and their
   tests
   -

   #interop - Web Predictability and Interop: Marionette, Webdriver and Web
   Platform Tests


If you are unsure of where your question may fall feel free to try any of
the channels listed and you will be directed to the best team to help.


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