Gijs Kruitbosch writes:
>> What if it causes a regression and a blocking bug needs to be filed?
> Then you file a bug and needinfo the person who landed the commit
> (which one would generally do anyway, besides just marking it
> blocking the regressor).
I find the association of multiple regress
On Fri, Feb 3, 2017 at 12:52 PM, Emma Humphries wrote:
>
> Pulsebot has been suspended when we found it was spamming 5-digit bmo bugs
> about GitHub issues.
>
> There's a ticket to clean up bmo https://bugzilla.mozilla.org/
> show_bug.cgi?id=1336563 and I'll work with that team to get it cleaned
Also, thanks to :jld for alerting me to the situation. -- Emma
On Fri, Feb 3, 2017 at 12:52 PM, Emma Humphries wrote:
> Pulsebot has been suspended when we found it was spamming 5-digit bmo bugs
> about GitHub issues.
>
> There's a ticket to clean up bmo https://bugzilla.mozilla.org/
> show_bug.
Pulsebot has been suspended when we found it was spamming 5-digit bmo bugs
about GitHub issues.
There's a ticket to clean up bmo
https://bugzilla.mozilla.org/show_bug.cgi?id=1336563 and I'll work with
that team to get it cleaned up.
Please reach out to bmo-ad...@mozilla.org so we can work with ev
Ideally we would be doing it in a way that we can audit things quickly in
the case we think a bad actor has compromised someone's machine.
While we can say what we want and how we want the process, we need to work
with what we have until we have a better process. This could be between now
and the
Thanks for checking the developer guidelines and making sure they are
consistent.
I'd like to hear a little more about:
branch merges - … I personally wish that especially significant merges
*did* have bugs to make it a little easier to track problems back to a
branch landing and have a place for
On 02/03/2017 09:29 AM, Gijs Kruitbosch wrote:
On 03/02/2017 15:11, Ryan VanderMeulen wrote:
A friendly reminder that per the MDN commit rules, the use of "No
bug" in the commit message is to be used sparingly - in general for
minor things like whitespace changes/comment fixes/etc where
tracea
On 03/02/2017 15:11, Ryan VanderMeulen wrote:
A friendly reminder that per the MDN commit rules, the use of "No bug"
in the commit message is to be used sparingly - in general for minor
things like whitespace changes/comment fixes/etc where traceability
isn't as important.
https://developer.mo
On Fri, Feb 3, 2017 at 7:11 AM, Ryan VanderMeulen wrote:
> A friendly reminder that per the MDN commit rules, the use of "No bug" in
> the commit message is to be used sparingly - in general for minor things
> like whitespace changes/comment fixes/etc where traceability isn't as
> important.
> ht
I have raised a bug[1] to block these types of commits in the future. This
is an unnecessary risk that we are taking.
I also think that we need to remove this as acceptable practice from the
MDN page.
David
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1336459
On 3 February 2017 at 15:11, Ry
A friendly reminder that per the MDN commit rules, the use of "No bug" in
the commit message is to be used sparingly - in general for minor things
like whitespace changes/comment fixes/etc where traceability isn't as
important.
https://developer.mozilla.org/docs/Mozilla/Developer_guide/Committing_R
25 Kasım 2016 Cuma 00:49:58 UTC+2 tarihinde Ralph Giles yazdı:
> tl;dr This is a heads-up that all gecko developers should install rust.
>
> Next week I plan to switch our default build config to require Rust
> when building Firefox.[1] If you compile Firefox from the C++ source,
> please install
12 matches
Mail list logo
