Want 2.4.x to be released faster? Help test feedback tickets!
With any release, there are inevitably a number of issues waiting in the "feedback" state. That is, they are supposed to be fixed but we are waiting on feedback from users to determine if issues can really be closed. In some cases they may not be fixed, and we need additional information or confirmation.
These tickets can be seen here:
It helps speed up the development process if everyone goes through the list and tests a few of the tickets.
Please update to a current snapshot before testing!
- If the issue is still not fixed, say so in the ticket and we can set it back to 'new' and work on it some more.
- If the issue is fixed, say so in the ticket and we can mark it resolved it and move on.
- If you see a ticket that already has feedback saying it is resolved, but the ticket is still open, let us know so it can be closed.
Any input is appreciated, thanks!
A number of Redmine tickets are still showing open when we have marked them as fixed, eg #7330 which I fixed on Sunday and has now been merged. There are others still showing open that are fixed. Is there a better way of informing those who can close them that it should be done?
Normally with the right text in the commit messages, that happens automatically. See: https://doc.pfsense.org/index.php/Referencing_Tickets_in_Commit_Messages and https://doc.pfsense.org/index.php/Developer_Style_Guide#Developer_Rules (some of which I just added)
If there is a ticket marked open which should be in a Feedback state, drop a comment on there and one of us can change the status.
@jimp Is this thread still valid? The ticket link is 404.
This post is deleted!
chpalmer last edited by
While the subject of this particular thread had already been released the fact that there are always feedback tickets available to test will always be true.
Release version is 2.4.3 right now.
I updated the link and some text in the initial post of the thread. It's still useful to get feedback tickets tested, though the version we need tested changes regularly :-)
@jimp Thanks! I feel I need to pitch in more QA where I can since I don't code anymore.