Oh, do you mean that nobody doesn't have concrete scenarios when
developers need to touch CLOBBER?
When not touching CLOBBER causes build failure at autoland, will it be
fixed by a follow up landing which touches CLOBBER or backed out and
need to reland same patches with touching CLOBBER?
If it's the latter, there should be listed up the scenarios in MDN or
somewhere. (Although, even if it's the former, such document must be
helpful for anybody work on managing the tree.)
On 2016/12/17 2:22, Benoit Girard wrote:
One of my goal when introducing CLOBBER was to document what was causing us
to CLOBBER so that we could audit and fix them if we ever found the time.
You can get a pretty good idea by going through the history of the file.
I don't believe anyone has taken to time to go through the CLOBBER hg
history to find the causes and document them. That could be interesting.
On Fri, Dec 16, 2016 at 12:16 AM, Masayuki Nakano <masay...@d-toybox.com>
wrote:
Hi,
I'm looking for some documents which explain when we need to touch CLOBBER
to avoid build failure. However, I've not found such document yet. I see
such information only in CLOBBER about WebIDL change.
So, is there any document which lists up when we need to touch CLOBBER?
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
_______________________________________________
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
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
