IMO we really need to get to a point where we have an active development 'mainline' with CI and nightly regression. Every project I've worked on since the 90s has had this and I'm sure many of us have this at least internally. It dramatically reduces cost of integration, need for rebasing, identification of problematic submissions, and other overhead and bottlenecks....
Lou On 6/15/2016 5:27 AM, Paul Jakma wrote: > On Wed, 15 Jun 2016, Jafar Al-Gharaibeh wrote: > >> Get the obvious ones quickly then and leave the non obvious for the "slow" >> process/review. > Right. > > The essence of my comment is that there isn't a good way to fast-track a > small set of 'obvious' fixes ahead of everything else. Instead, it is > the "non-obvious" that will make themselves apparent in various ways; CI > systems will find issues, people will object to things they see and find > objectionable. > > I.e., it's not easy to prioritise the "easy" stuff (particularly not in > an /objective/ way - and non-objective integration causes issues) and > fast-track it. It is however easy to identify the 'hard' stuff, that's > objectively the stuff that generates emails on the list. :) So we can > objectively sort that lower. > > regards, _______________________________________________ Quagga-dev mailing list Quagga-dev@lists.quagga.net https://lists.quagga.net/mailman/listinfo/quagga-dev
