If you release less frequent, there are more changes that go into the code. So you could counter-argue that if they donāt manage to handle all the bugs with the little changes between the versions they have now, how should they cope with much more changes?
Yes, and nobody is expecting it so urgently that they canāt wait a week or so.
The problem is simply the lazyness. Start a google search, find an officially document and stop searching.
That is ok for the forum, but not for a release planning of an app to keep track with the compatibility. The forum is no developerās source.
@szaimen directed to the correct source. It is just hard to find/remember, because the Github wiki is a little bit āhiddenā. And itās the eighth google hit; although at least it is on the first page for me. Maybe it is just a personal issue.
Linking the wikipage on all relevant places should do the job.
Thatās what I wanted to say. Additionally a link in the breaking changes issue sound like a good idea too to me.
I have no idea, if the effort maintaining the page is valuable or not. In the first step, I would just add a prominent link link to the current schedule to avoid the dead end there for people like me.
Maybe little late (as there is no docker beta release) I updated my DEV instance on docker to NC24.0.0.12 and I have to admit it worked like a charm! congrats!
I see this a sign of improving quality as learning from the huge issues we suffered shortly. keep going! good job and thank you everybody who was working on this release!