On Wed, 13 Oct 2021 at 09:00, Martin Entlicher <[email protected]> wrote: > I'd say that the best approach in this case is to create an issue for this > problem and fix the issue. > I did not notice that others would revert their work as soon as a bug occurs. > Everyone introduces a bug from time to time. And usually, we're able to fix > them. > > The given commit was a bit more risky as it had to touch the core > functionality. It usually takes some time till the product is completely > tested.
Personally I think Matthias took the right approach here, and in fact an approach I think we should take more often (hence my +1 comment on the revert PR). We agreed to work under the general principle of keeping master releasable. The issue had been raised on the original PR for almost a week before the revert PR, which was also open almost a week before integrating. > Thanks for finding it, I'm going to address the issue... Thanks. Will keep an eye for it. Am about to do an email delaying freeze for a week to try and get nb-javac in. Be good to get this issue fully fixed before then too. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
