developer branches and release process

[venkatrag1]

cc: @mimir-d who brought this up in the T&V forum today, and suggested some ideas that I'll capture here.

So far the contribution model for CTAM has been for different partners to create their own long standing developer_* branches and make PRs against these, and periodically to merge these into developer branch.

This creates the overhead of having to constantly rebase this developer_* branch against the primary developer branch after the merges.

We wanted to propose squashing these developer_* branches and making PRs directly against main developer, and handing the review POCs through tagging in the PR itself. Any feature branches that exist in the fork will be short-lived that way and wouldn't have to worry about constantly rebasing.

Also wanted to kick-start a discussion on releasing into main branch from the developer branch so that internal repos of various consumers can use the quantized releases in the main branch instead of having to keep track of diff-by-diff changes in developer branch.