I know the secret on why there is no planned release as of now but i will keep it to myself and not share it with anyone, mwahahahahah ahem...
(10-04-2014, 08:48 AM)pokemontrainer Wrote: [ -> ]Couldn't some devs just start working on blocker bugs and current milestone bugs right now without waiting for a feature freeze? Unless new updates are constantly introducing regressions, I don't see why there need to be a feature freeze for work to start on a stable release.
Sure, but since all of the developers donate their time for free, they also get to choose what to spend their time doing. If nobody wants to work on bug fixes, then that task doesn't get done right away. Most of them probably want to work on ideas they find exciting, and tracking bugs in other people's code probably doesn't rank high on their lists.
(10-04-2014, 08:48 AM)pokemontrainer Wrote: [ -> ]Couldn't some devs just start working on blocker bugs and current milestone bugs right now without waiting for a feature freeze? Unless new updates are constantly introducing regressions, I don't see why there need to be a feature freeze for work to start on a stable release.
Yes, that's how it has to happen. We aren't going to start taking steps towards a release until after most serious regressions have already been fixed.
Of course the point of the feature freeze was to prevent new bugs from sneaking in while fixing old bugs. The lazy feature freeze of 4.0 is what resulted in 4.0.1 (comex
). While we have a lot better review system in place now, there are a lot of things that just aren't tested commonly *cough JITIL cough*.
It will be interesting to watch at least.
If only I knew coding. I'd really love to help but lack knowledge in that field. I mean it has been quite a few years and this year seemed to be very progressive, I just wish I could help speed things up though I'm sure though some problems may seem easy they're actually quite a pain to fix.