On 02/06/17 15:11, Tim Penhey wrote: > Hi all, > > Sorry for the weird encrypted one. > > The date for the release candidate is Tuesday the 6th of June. We really > wanted to get it out this week, but we hit two issues that we just had > to get done before the release candidate. We decided that a few extra > days for a better quality release was worth it. > > On Tuesday we will be branching develop into a 2.2 branch. Also, we are > enacting a slightly different policy around landing changes into the 2.2 > branch during the RC period. No extra bug fixes will be landed in 2.2 > once the release candidate has been cut unless it is a critical > regression, in which case another candidate will be released. The > intention here is that the release candidate will be a true candidate, > and not just be another week to get fixes in before the final release. > Once we have confirmation from Solutions QA and JAAS that they are happy > with the release candidate, we will release is as 2.0.0 2.2.0 maybe? > final. Once this > happens the landing restrictions will be lifted on the 2.2 branch. > > We already have a number of bugs that we want to get fixed for 2.2.1. > Bugs that we have decided need to be fixed and put into the user's hands > before the 2.3 release, which won't be for a number of months. > > The notable fixes of the last week: > * a number of race test fixes, Go 1.8 found more than 1.6 > * long awaited log compression during log rotation > * additional configuration around max txn log size so large controllers > can better handle large workloads happening very quickly > * issues with migrating models that use local charms > > There are just a couple more changes that we hope to land over the next > day, that will improve performance on larger models. > > Also, the 2.2-rc1 milestone on Launchpad got significantly cleaned up. > There were bugs that were marked as high priority that had been bounced > from milestone to milestone with no one addressing them. These have been > removed from milestones as they just weren't getting addressed that way. > > A lot of work has gone into the CI infrastructure this week to make it > more robust and to produce less noise on the test runs. We are looking > much better across all the CI tests. There are a few intermittent tests > still bugging us, and a few CI tests that needed updating due to changes > that landed over the week. On the whole though, we are very happy with > the stability and robustness of this upcoming release. > > Cheers, > Tim >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
