On Aug 12, 2013, at 10:11 PM, Andreas Gal <[email protected]> wrote:
> > Lloyd Hilaiel wrote: >> >> On Aug 12, 2013, at 4:27 PM, Johnathan Nightingale <[email protected]> >> wrote: >> >>> On Aug 9, 2013, at 9:11 PM, Mark Finkle wrote: >>> >>>> My only strong opinions are: >>>> >>>> 1. Using bugzilla as the one source of truth for bugs. Even b2g had to do >>>> it. >>>> 2. ELM is the place where the code ends up for nightly builds. How it gets >>>> there, I don't care. But we have a test infra that works with the hg repos >>>> and we need it to run. >>> >>> A +1 to both of these, but particularly the first - it has been our >>> experience over and over that when we move away from bugzilla as the source >>> of truth, it bites us in numerous and unpleasant ways. At this point, it's >>> the nearest thing you'll encounter to a project-wide edict, but it's >>> absolute law when it comes to work that impacts Firefox desktop, Android, >>> or OS. >> >> I'm hearing the same thing from everyone. >> >> decision: >> 1. As far as the client engineering team - "ELM is the place where code ends >> up" - it doesn't matter how it gets there. >> 2. Anything that has cross-team implications (like say, gavin needs to >> review a patch from lloyd), goes in bugzilla. > Everything has cross-team implications. If the sync team is twiddling away on > 3 more internal bugs and release team is tracking that, they are doing that > via bugzilla. If you would like to work on a product at Mozilla, please do it > with bugzilla. Nobody is a big fan of bugzilla, but its what as a project we > are setup to use. Just stick to it and lets move on and not waste energy on > reinventing this part of the software engineering process. Loud and clear. Let's use bugzilla for sync work. Let's not make the issue broader than is necessary for this list - if you're uncomfortable with projects that use different tools, there are better forums for discussing that. lloyd > > Andreas >> >> good? >> >> lloyd >> >> (P.S. My desire was to craft out a short set of milestones with minutiae, >> like "add a preference for disabling new sync", or "determine where >> implementation will land in the client" or "implement container for >> authentication" - I'll just do this in a etherpad, that works for me.) >> >>> J >>> >>> --- >>> Johnathan Nightingale >>> VP Firefox Engineering >>> @johnath >>> >> >> _______________________________________________ >> Sync-dev mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/sync-dev
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
