> > I think bug reporters and testers did their job during the development > > stage, the bug slashing weekend and the community contribution to 10.3 > > were probably the biggest since the birth of the project. > > > > As a consequence, I think some more effort to fix at least the most > > annoying bugs, some more care in trying patches even with the > > cooperation of the community, and a somewhat less restrictive approach > > to patch releases (we are at "only security stuff" now) should be really > > considered. > > I agree, but you will need to convince coolo or the board when that > starts functioning to change this policy.
Thanks for your answer. I will try for sure. I perfectly understand the potential risk of making this policy less strict, because of the work it would add to the teams and also to the increase of requests it might lead to. What we need, I think, is a set of criteria to follow to decide if a not security related patch is necessary, with a reduced and clear set of cases, like impossibility to use functions which should already be present in the released version, to exclude the request of fully new packages, which is not the goal. We should try to discuss this in a status meeting, if possible. With kind regards, Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
