LCS should support uploading and deploying multiple CSU extension packages (packages from different ISV/Partners and Customers) and show different packages deployed in the LCS UI.
This will avoid the manual merge of the packages from different ISVs and Partners and enable seamless deployment without involving any Dev persona for upgrade.
Comments
Big plus one
Category: Extensibility and Developer experience
That's a great suggestion by Bryon. + 1
Category: Extensibility and Developer experience
To build on this, it would also be nice if CSU deployment to Production could follow the notion of F&O, where we could take the resultant state of deployments to tier 2+ environments (where you may have deployed x # of ISV packages and a customer extension package), and take that whole set along with the Platform version as one deployment to Production (to help us ensure we only run code in production that has run together in lower environments, and ideally even tested!).
Category: Extensibility and Developer experience