Rename "Debug" to "Development"

[hryx]

The existing build modes are Debug, ReleaseFast, ReleaseSafe, and ReleaseSmall. The default is Debug. This is a good default because unreachables and array bounds violations will alert developers reliably. But I think the word "debug" does not accurately describe this mode.

Debugging is a special process you go through to find the source of a problem; it's something you hope you don't have to do, and only happens when something is wrong. The name of the entire, normal process up to the point of releasing is development.

I think we should rename Debug mode to Development (or Develop) to better reflect its usage and role in the software lifecycle and to avoid a negative connotation. Thoughts?

🤔 <(hmmm)

[andrewrk]

Related: #978

[andrewrk]

One thing to consider is, say, if your main build mode is ReleaseFast, and then you want to troubleshoot a problem in one particular area so you use @optimizeFor(.Development). It would be slightly weird to ship that to production, even though that's exactly what you want to do.

[andrewrk]

I don't have a terribly strong opinion on this, but I'm going to close it in favor of status quo. I think Debug and Development mean roughly the same thing in this context. I do like that when switching from Debug to Release, there is an implication that you fixed all the bugs. Which makes you think, when selecting:

• ReleaseSafe
• ReleaseSmall
• ReleaseFast
  With this implication that "Release" means you fixed the bugs, if you're not so sure the bugs are fixed, then you'll be more inclined to pick "Safe".