Also, if there are disagreements on a direction among members then it is usually the case that a -1 from a binding vote requires a revert and starting a discussion. Then we can either have consensus, lazy consensus or the issue is shut down.
I'm saying what should be done, just laying out the standard rules we usually run by. On Thu, Dec 19, 2019, 1:59 PM Taher Alkhateeb <slidingfilame...@gmail.com> wrote: > May I suggest inquiring from the community on whether this feature is > important to them? Pehaps on user@? This way maybe we can have a more > informed decision on whether to adopt this change. > > On Thu, Dec 19, 2019, 10:13 AM Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > >> Le 18/12/2019 à 21:09, Jacques Le Roux a écrit : >> > Hi Samuel, All, >> > >> > Le 18/12/2019 à 14:00, Samuel Trégouët a écrit : Le 18/12/2019 à 12:09, >> Jacques Le Roux a écrit : >> >>>> Mathieu asks Michael to provide an "explanation regarding why it >> matters in production environments to be able to patch" component-load.xml >> files >> >> yes we are still waiting for your answer Michael ;) In my opinion we >> >> cannot go ahead in this discussion without your answer, without your >> >> need about component-load.xml: are you trying to avoid loading a >> >> particular framework component? do you patch a framework component and >> >> need another one to be loaded first to make your patch works? ... >> > >> > That's an interesting point indeed. Have you your own framework >> component/s Michael ? >> >> Note: I include applications components here >> >> >> Jacques >> >
