What ever you want. we released as 2.6 -beta and 3.0 -beta because, while the SCM API changes, the impact on the Git plugin is minor... it is just the downstream impact of unwinding hacks in github branch source and bitbucket branch source that makes it part of the coordinated release train.
On 4 January 2017 at 12:24, Mark Waite <[email protected]> wrote: > You're welcome to do the releases. Don't forget that the 2.6 release must > be built with Java 7. The 3.0 release can be built with Java 8. > > Since this is a larger change in api, will it be 3.1 and 2.7? > > Mark Waite > > On Wed, Jan 4, 2017, 3:17 AM Stephen Connolly < > [email protected]> wrote: > >> Mark, >> >> I am looking to push the branch-api 2.0 changes out as non-beta releases. >> I will need to coordinate releases of Git plugin. Am I OK to cut the >> releases of the Git plugin, or do you want to tangle yourself into the >> coordinated release chain? >> >> -Stephen >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxsoj1kDZU_PZdKJ4dBSSxjwCAZWL%3Dua0OGABteRFtfLg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
