On Thu, Apr 17, 2014 at 11:51 AM, Paul Allen <[email protected]> wrote: > Whilst the new plugin provides all the basic SCM functions, it is not yet as > feature rich. We plan to add features […] > > […] perhaps there is a way to branch (fork) the old codebase into a legacy > area?
A bit more work, but arguably better for users, would be to include the new refactored implementation inside the existing plugin (in trunk versions). For a time, users of the plugin would see two SCM options—Perforce (v1) and Perforce (v2)—with somewhat different configuration UIs and functionality. They could experiment with switching to v2, or go back for a while, on a project-by-project basis. You could even decide that v1 configurations restricted to a certain set of commonly used features would be safe to automatically upgrade (i.e., readResolve) to a v2 configuration. Eventually the v1 implementation could be dropped, or rather exist only as a class with a readResolve method. This is of course assuming that the current maintainer(s) of perforce-plugin are aware of your effort and on board with it. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
