Task

As discussed in the Feb 19 COPE call:

Today, we have a problem with Community/DP plugins where the overlays repo is locked down to a Z stream BS version but continues to pull updates from rhdh-plugins (and likely bcp) intended for the vNext stream.   This happens because the overlays repo assumes all changes are in scope until the next BS update which is untrue.  This has resulted in an error prone process that has falsely tagged vNext updates for the Z stream.  

Current workarounds mean the plugin teams need to be extra careful when merging PRs. 

We need to clarify the process to include:

1. When vNext changes can be updated.  Perhaps have some automation to disregard changes based on target versions
2. What is the patch process if bugfixes are required on the Z stream?
3. Is it clear that once release branches are created, plugin teams should no longer commit changes in rhdh-plugins/bcp?
4. How to delete tags if they are erroneously created

Background

Dependencies and Blockers

QE impacted work
Documentation impacted work 

Acceptance Criteria