(Again, sorry for not noticing this earlier, I’m going to work on a “How to enable forum notifications” post)
Yes, I think it is. For Juniper, four weeks was just right – even though we eventually went beyond schedule to announce the release, most of the testing was done during those first four weeks. For Koa, I did some initial testing and I expect that fewer issues will arise.
Thus, I’d like to propose the following schedule:
2020-09-27T22:00:00Z: start testing the master branches to detect major changes early. We should not spend too much time on this, as the master branch is likely to change drastically before the code freeze. However, I’d like to have a very rough idea of what’s to come in Koa. In particular:
- Which dependencies (Mongodb, MySQL, Python, Nodejs…) were upgraded?
- Are there any new IDAs or MFEs?
Answering these questions will help us have a clue of what’s to come in Koa, as we still don’t have a changelog for Open edX. (yes, I will keep highlighting this fact in a passive-aggressive manner until it is no longer true)
2020-11-08T23:00:00Z: feature freeze, creation of the open-release/koa.master branch. The community starts testing and reverse engineering the new release, fix bugs. Note that we will not be creating “open-release/koa.alphaX” tags.
2020-12-08T23:00:00Z: publication of the open-release/koa.1 tag, announcement, champagne