The first release candidate of 1.2.16rc1 turned out to still have a tiny bug with the new release channel feature, and since that meant a second release candidate for 1.2.16 was necessary to fix that I also took the opportunity to take care of two other things reported in the mean time.

If you are already running 1.2.16rc1 and followed the instructions in the announcement of 1.2.16rc1 including the switch of the release channel to “Maintenance RCs” you should soon get an update notification just like you are used to from stable releases. Please report back on the bug tracker (links below) if anything goes wrong here. I actually consider it lucky that I had to push out a second RC for the simple reason that you’ll now also be able to test the new RC update path ;)

If you are not yet running 1.2.16rc1 but want to give this RC a test drive, you’ll need to follow the manual instructions as found in the announcement of 1.2.16rc1.

If you are not interested in helping to test release candidates, just ignore this post, 1.2.16 stable will hit your instance via the usual way once it’s ready :)

You can find the full changelog and release notes as usual on Github.

Depending on how the feedback for this release candidate turns out, I’ll either look into releasing 1.2.16 or fix any observed regressions and push out another release candidate within the next week.