Trying to grasp Content Views and Life Cycle environments

I thought I finally got how content views and life cycle environments work but I'm not able to grasp how to get a single in-house package promoted. I'm starting to think I need to redo my Environment.

My environment path is

'Library' with 3 Environments, Dev, Test and Prod.

For the sake of simplicity I have 1 content view for each version of Red Hat we are supporting.
My Content view "RHEL7 All" contains the RHEL7 Products I need plus "EPEL", and a "Custom" repo where our in house packages are placed.

The work flow is as follows:

• 2nd Tuesday of month I Publish a new version (Version 4.0 for example) and Promote to Dev. The content is everything - about 36600 packages, 5400 Errata. No filters used.
• 3rd Tuesday of the month I promote to Test
• 4th Tuesday of the month I promote to Prod.

New month I repeat, creating a version 5.0

Now I want to make an rpm available to all environments which is uploaded to the Custom Repo, without promoting anything else such as errata or other packages. Do I use a filter within the 'RHEL7 All' Content view for just the one package and promote it through to production, then Delete the filter when done?