A big thank you! You fixed annoying and long-standing bugs.
Yes, please just close them. If the reporter can nevertheless reproduce, he will reply. This way of handling bugs is in my experience a good way. It might appear harsh but we did so in the Software project LyX (that I worked for before I came to FC) and it turned out to be effective since before, we smothered in bug reports and it cost us so much time to look through them again and again.For some of them I cannot reproduce (I have posted in the relevant threads). I think it would make sense to close those in which nobody can no longer reproduce.
Good question That there is no such criteria, nor a release maintainer etc. is the last FC mystery for meDo we have a release criteria? (a preliminary release date or a minimum number of features or fixes we want to include)
Werner, Yorik, can we please set up something transparent to get to a release? What about a Wiki page where you input the TODOs from your perspective? Others can have a look and help out in reviewing pending PRs etc. I mean we have some manpower, so some person can be the release maintainer for translations, another one for the documentation, another one for pending PRs, another one for the website (news etc.) and another one for the open bugs.
This way we distribute the workload and encourage the developers since we have a transparent way for a release and everybody can join one of the mentioned fields.
Can you both please make a statement accordingly?
Since there is nothing better than doing it, lets ask around who wants to take over a part for the release? I set up a Wiki page to fill in the names: Release_of_FC_0.19
I still really believe version 1.0 should follow 0.19 if realthunder's toponaming stuff went in.EDIT: BTW, I have created the 0.20 version in the bugtracker,
yorik wrote: .