I have a quick question on the best practices for managing the Parter Business Org when developing Second Generation Packages. As Parter Business Org act as the Dev Hub for the second generation packaging and the dev hub owns the packages (which can not be changed once the package is generated), what is the best practice on handling CI/CD process. Before we deploy the final package to production which will be on Parter Business Org Dev Hub org, we need to build and test the packages many times as beta features in a CI org. We many times need to have many CI processes which will have the same package names. These are just beta packages and we don't want to deploy these to the Parter Business Org yet.
So what is the best practices being followed for this? Do you guys use the same Parter Business Org for all these purposes (I hope this is not the case) or you guys request new org with dev hub for incorporating CI/CD purposes.
I would like to get some suggestion on what is the best practices being followed in this.