Terminal.Gui v2 Alpha Release Criterion

These are the criteria we will use to decide whether V2 Alpha can be released.

Unitl the Alpha is released, we will not accept any PR into v2_develop that does not meet these criteria.

By taking this approach we can get all contributors focused on a release and get it out as quickly as possible.

V2 Alpha Goals

These are the criteria we will use to decide whether V2 Alpha can be released.

Unitl the Alpha is released, we will not accept any PR into v2_develop that does not meet these criteria.

By taking this approach we can get all contributors focused on a release and get it out as quickly as possible.

Make v2_develop the primary Terminal.Gui branch
Publish v2.0.0.0-alpha package on nuget
CI/CD is setup for long-term support. This means the v2_develop is the default branch, the v2 API docs are primary, and v1 can be supported in parallel. It also means we have a branching strategy that supports parallel development of post-Beta, and post-v2 features while we're supporting the Beta.

0 - Development is Blocked. Nothing is more important than fixing immediately. All pri 0 Issues must have an owner set. If the owner can't work on the Issue immediately, he/she will assign it to someone who can.
1 - Release Blocker - Issue needs to be resolved in order to ship the Release. We will not release until this issue is addressed. All pri 1 Issues must have an owner set. That individual is responsible for doing whatever it takes to get the Issue resolved as quickly as possible. If the owner can't work on the issue, they are responsible for finding someone else to take ownership.
2 - Nice to Have. We want this issue fixed in the Release, but we will ship without it and address it later if we can't get it done in time. Ideally, pri2 issues have an owner set, but don't have to.
3 - Not in Release. The Issue will not be addressed in this release but may be in a later one.