Git Wizard Workflow and Saving Versions

Question

I want to get started with the git workflow, so I went ahead and started to read a lot. Including:

• atlassian tutorial
• nvie article

I have a few questions regarding this model:

• What is the purpose of the lead branch?
  I know this is a production history, but why do I need it if I have actual release branches?
  I assume that the release branches were deleted at some point, so the only story is in the wizard tags.
  Am I right in thinking that you can either have a main branch, or delete all release branches, or save release branches and not have a history branch (as leading)?
• Assuming we do not have such frequent releases. Is it better to use a wizard approach or maintain a branch approach?
• I see facebook in react and react-native uses a "keep branches" approach. why?

Answer 1

• What is the purpose of the main branch?

This is the default cloned branch, so any repo cloning can start from the last known good production point.
Release delimiters are intended to start the next release cycle, so the old ones can be reduced in the end, because they are intended to merge with the master after the release development cycle is completed.

2. Assuming we do not have such frequent releases. Is it better to use a wizard approach or maintain a branch approach?

, .

3. , facebook - " ". ?

, . .