So there is the UI refactoring that should make configuration easier to understand: instead of 6 checkboxes with 64 possible combinations that are hard to comprehend and identify which combinations are nonsensical... there are three "discovery" traits that control discovery of origin branches, origin PRs and fork PRs
New functionality is that we can now expose as traits configuration of the git extensions, so if you want to checkout to a local branch rather than a detached head, if you want to control submodule behaviour, etc that is all now available (we also remove the git extensions options that are incompatible with branch sources to stop people complaining when they don't work) New functionality is that - by default - we only clone the minimal ref specs required (add the advanced clone behaviour trait and it will be back to as before) New functionality is that we can use shared code for filtering repositories and branches by wild cards or by regex (and somebody can add Glob style wild cards via an extension plugin and *everyone* gets them!) Then there are the subtle bugs that I fixed due to the better testability of the trait approach Then Bitbucket gets merge commits (except mercurial repositories on Bitbucket cloud... but I hope to address that once I figure out how to get mercurial to do the merges) I claim that the data migration is fully tested... so what I am looking for from testers is: * any issues with data migration * any branches / PRs that were present before and have now disappeared on first rescan after upgrade * any branches / PRs that fall in a "rebuild" storm after upgrade / rescan I believe there should be none of these issues but we need testing from other people's real configuration before we can push an non-beta release for a set of changes this big (40k LoC in the diffs... though a lot - at least half - of that is new tests) On Sat 17 Jun 2017 at 07:43, Łukasz Zachulski <lzachul...@gmail.com> wrote: > Can you summarize what can be expected from those new versions > Is it really only UI refactoring or do changes introduce something more? > > -- > 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/6cd55d5c-ea28-4342-9da3-bda8eae1262f%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- 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/CA%2BnPnMye%2BQEP347495wP5OgiRgOLmdmy%3DnQkgVKHXEMhk3nNVQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
