Alternate development landscape and transport path - release management
We are discussing a proposal within our company to build a landscape that includes separate clients and transport paths for development of new system enhancements vs. ongoing production support. The idea is to keep all new development in a separate stream and prevent any conflicts with any required production support changes. This approach was used on a project where I previously worked, and we are seeking input from other SAP shops that use this approach, as well as any best practice documentation to assist us in development of an internal proposal on the topic. I would be grateful for any input on this topic, as well as the topic of release management. I have done quite a bit of searching on SDN and BPX and am just not finding anything.
Note that I also posted this question in the BPX general discussion forum because I was not clear exactly how it should be categorized. I apologize if this was not the appropriate course of action.