We should definitively try to not be too sloppy and always have our dev branch in a working state.
At the same time there’s should some tolerance for regressions in non critical aspects. It’s an essential part of an iterative dev process: move fast and adjust as you go. It there’s 0 tolerance for regressions we will get into a conservative mindset where people just want to move bits around and not take on any substantial piece of work. The more ambitious people will work out of separate branches to do what they have to do and dump everything on the main repo as late as possible. New features will be exposed to dogfooders too late in the cycle to uncover bugs and collect proper feedback. People have to understand that dogfooding carries some risk. I worked at Apple within the iOS team and there were perf and power consumption regressions all the time in the nightly builds. You, of course, keep an eye not the stats and want to hit the numbers before release but regressions during the dev cycle should not be stigmatized. Diego. > On Oct 2, 2015, at 10:16 AM, Fabrice Desré <[email protected]> wrote: > > On 10/02/2015 09:49 AM, Justin D'Arcangelo wrote: >> I would also like to add that this policy of immediately pouncing on devs >> who attempt to try something new that may cause the perf numbers to >> momentarily dip is part of why we seem to have a culture problem in FxOS dev >> where everyone is afraid to take any kind of risks. If we are not allowed to >> have a 2-3 week window to optimize after a huge landing such as this, then >> how are we supposed to experiment or take risks? > > You have all the time you want if you don't put dogfooders at risk. No > one is saying that you should not take the risk to try something new > (side note, you spent enough time on spark & flyweb to know that). But > when it comes to shipping there is a minimum bar to meet, and with > basically a x2 memory usage we are not meeting it in this app yet, > sorry. Feel free to ship a new app alongside the existing one instead > and ask people to try it, since we can't do A/B testing. > > The problem we have is that most people don't care enough about having a > stable nightly, which is why we haven't updated dogfooders for more than > a month now. > > Fabrice > -- > Fabrice Desré > b2g team > Mozilla Corporation > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
