Not all work fits neatly into a release plan, and that's okay. Especially in the curriculum, contributions of any kind can reasonably take place at any time. The purpose of a release plan isn't to put limits on the work that can be done for a release, but rather to ensure that the important things that really need to get done are accounted for. If you want to work on something that's not explicitly asked for in the release plan, that's totally fine.
masterbranch of the curriculum are properly represented in the PTR. This should automatically happen nightly, but someone from the NRE Labs Ops team will make sure this is true.
Instead of submitting feedback, you may feel like you can just fix it yourself in a Pull Request. This is always welcome and appreciated, and is often the easiest way to make your first contribution to the curriculum. So, don't be shy! See the curriculum contribution guide for more info on how to do this.
master, as represented via the PTR site represents a healthy curriculum.
v0.4.0of the platform was released simultaneously with
v1.0.0of the NRE Labs curriculum. In the future, the curriculum may want to release a new version before
v0.5.0of the platform is ready. In this case, the curriculum, starting with
v1.1.0will continue to target
v0.4.0until a suitable stable platform release is ready.