This evening (on the old continent), we had a meeting with @nedbat and @sambapete to discuss the creation of the “open-release/juniper.master” branch. There has been a lot of testing from the community in the past couple weeks, all blocking issues have been resolved, and we were confident that we would be able to create this branch today.
This branch is a requirement, but it’s not the actual release of Juniper. Technically, Juniper is only released when the “open-release/juniper.1” branch is created. However, the juniper.1 branch is expected to follow up very quickly after the creation of the juniper.master branch.
Unfortunately, we could not create the juniper.master branch because we discovered an important issue in the current Juniper release candidate (RC2). The deployment playbooks run RC2 with an outdated version of MongoDB: they install MongoDB v3.2.16 instead of v3.6.17. This is a serious issue for a couple reasons:
- MongoDB v3.2 has reached its end-of-life in September 2018 and no longer receives security fixes (https://www.mongodb.com/support-policy).
- The upgrade from 3.2 and 3.6 is non-trivial and we cannot ask users to upgrade between the moment we release juniper.master and juniper.1.
- edX.org already runs v3.6, so Juniper would become outdated on the day it was released if it came with v3.2.
Thus, we decided to postpone the release of the juniper.master branch by at least a week. This is a 4-day weekend in the US, so there won’t be much time to get a PR reviewed to upgrade the deployment playbooks. A juniper.rc3 branch will be created, and we hope that many users will have the opportunity to test this third and (hopefully) final release candidate.
It remains an open question why the MongoDB upgrade (or lack thereof) went unnoticed by almost everyone in the community. I expect that the post-mortem investigation of this issue will give us great insights about the way we can improve the release process. In the meantime, thank you all for your hard work!