Presumably that decision would be made on the basis of such technical considerations as "How much poo are we likely to be in if we put this one off until Final?" and "How much poo are we likely to be in if we attempt to deal with this one for RC3?".
💩💩💩
Now that's a lot of poo
.
GitHub scares me, or rather intimidates me. I have totally no idea how it works, I appreciate your guidance...
It was kind of intimidating for me too, but actually, there's really nothing to it
. If you register a new account, all sorts of popups will start to appear that kind of guide you through the site
and on top of that, if you ever find yourself in a pickle, you can always Google your way out
.
Regarding reporting bugs, it works pretty much like a regular forum. You open a new "topic" and then the devs take a look at your "post" and try to replicate the bug you reported. If they can replicate it, the bug is confirmed. If not, in most cases, the bug report is dropped, but this also depends on the seriousness of the issue and if multiple users reported the same thing, but, for some reason, the devs can't replicate the behavior, etc., etc. So, in some cases, even though bugs can't be replicated, they're not marked as "bogus" bug reports, they're just kinda left for further analysis
.
Besides, you'll ease the developers jobs if you report bugs directly on GitHub. It's designed to work with code, so it's easier to see which bugs and/or feature requests have been fixed, implemented, rejected, etc.
.
