You use false when you don’t want to abort the thread. What that means is that false will cause the code to continue to execute. So lines of code which appear after the Response.Redirect will be executed. A true will just kill the thread so nothing further will execute, which in turn throws a ThreadAbortException.
So it’s really a judgment call based on how the rest of the code in that situation looks. Generally you want to put calls to Response.Redirect at the end of an execution path so that nothing further needs to be executed. But many times that’s not the case. It’s just a matter of how you control the logic flow in the code.
For example, if the next line after Response.Redirect is a return and the execution path simply ends, then you’re probably fine. But if there’s all kinds of logic and executing it in this case would leave the system in an unknown state, then you may want to abort the thread.
Personally I consider aborting the thread to be indicative of poor logic control. It’s similar to a well known code smell where exceptions are used to control logic flow, which is universally frowned upon. If you can control the logic flow without the need for aborting a thread and throwing an exception, that would probably be preferred.