On 24.03.2016, at 16:32, James Nord <[email protected]> wrote: > So where do fixes to the 2.0 go?
If they are intended to make it into 2.0, the '2.0' branch. If they are intended for 2.1, 'master' from next Wednesday on. (Or maybe build on top of 2.0, file against master now, and link to the 'real' diff without all of 2.0 in the PR description.) > I'm not sure why this is being treated differently from an LTS - which I > would guess 2.0 would be - otherwise why does it need stabilization - it's > similar yet different... If it's not a LTS version (as the next LTS version > has been choses and it wasn' t 2.0 why is this extra needed - how is this > different from weeklies?) Because there's a whole bunch of unusually large changes and a lot of attention on the final version. So I'd prefer we don't mess this up. > Is this a new process going forward No. We're going back to regular weeklies after the 2.0 release. (And I really hope this is the last release like this for a long time, another 11 years would be fine with me.) It will also not disrupt the LTS schedule: We're scheduled to choose a baseline in July. It is very likely to be a 2.x, but that's just because by then the releases of the previous ~10 weeks will have been 2.x. > IIRC it was also stated that there was going to be a code review of 2.0 > before - I guess this is the initial merge 2.0 branch to master - is that no > longer planned/ being swept under the carpet? I don't see how this is remotely practical given the scope of changes that went into the 2.0 branch. So if you held off reviewing things and filing issues until now, please do so now. > - otherwise I would have probably been a lot more diligent / rigorous on code > reviewing all the changes going in. There are some known issues with some of the changes in the 2.0 branch that need to be fixed before 2.0 RC. Those have been filed in Jira. But other than that, everyone had plenty of time to comment on the the PRs. -- 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/66F876F7-AAB0-4015-A34E-07903D3409C2%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
