I am grateful that all the most powerful AI engines all scan #curl to find flaws. Finding them means we can fix them.
Sometimes it just demands coming up to the surface for a few deep breaths before we dive again.
Discussion
I am grateful that all the most powerful AI engines all scan #curl to find flaws. Finding them means we can fix them.
Sometimes it just demands coming up to the surface for a few deep breaths before we dive again.
@bagder Sounds easier if you can scan curl for these bugs before you release new versions so you don't commit new bugs that AI can find.
@breakin everyone is scanning curl all the time. There is no particular pause or moment in time where nothing is happening...
@bagder Right, I was thinking that if you scanned before making releases new bugs (that ai can find) will not go out into releases at least. But if people use master then ofc there is no time when nothing happens, then you need to scan before committing things to master and that sounds painful.
I am guessing all new features get to live some time both in master and in a release candidate branch before eventually getting released. So there should be time to find bugs between merging to master and releasing the code.
@breakin whatever we do now is *before we release* so clearly all this is done before release