Hi Guys, We are working to add BlueOcean support for Perforce and have added the Perforce SCM under the 'blueocean-plugin' and following the pattern of the other SCM providers.
We had hoped to release the work in stages (Create first then Edit and other improvements later) however unlike other plugins we don't have control over the release process. Presumably we will raise a GitHub PR, wait for you to Merge the change, then wait until you release a new version of the BlueOcean plugin? How long (assuming that there are no code issues) would the typical turnaround be from submitting a PR until a customer can use a released version with the changes? Is there a way we can split some of the SCM implementation out into a seperate plugin to help decouple the release process? Kind regards, Paul -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a3dd731-46d3-4497-886e-68d1a04f4ced%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
