On 02/06/2017 08:19 AM, Mike Hoye wrote:
On 2017-02-03 2:01 PM, Steve Fink wrote:
Typo/whitespace - No bug is fine, but if it is associated with a
recent landing of some bug, then you should use that bug number
anyway. Makes uplifts cleaner.
Whitespace errors seem like a wierd thing for an
On 2017-02-03 2:01 PM, Steve Fink wrote:
Typo/whitespace - No bug is fine, but if it is associated with a
recent landing of some bug, then you should use that bug number
anyway. Makes uplifts cleaner.
Whitespace errors seem like a wierd thing for an engineer to be working
on?. Code cleanup
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
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
10 matches
Mail list logo
