Want 2.1 to be released faster? Help test feedback tickets!
-
[Shamelessly copied from the same post I did for 2.0]
Right now there are 75 tickets in "feedback" state for 2.1. That is, they are supposed to be fixed but we are waiting on feedback from users to determine if issues can really be closed.These tickets can be seen here:
http://redmine.pfsense.org/projects/pfsense/issues?query_id=28It would help speed up the development process if everyone would go through the list and test a few of the tickets.
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 close 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!
-
I have updated a few.
#2406
#2412
#804
Looking at others. -
I would love to help out but I have two problems:
-
I don't have a clue what the problems mean, from reading the subjects. I think these are all problems that go 'very much under the hood' (meaning: you need to have a lot of technical knowledge, which I have not)Â :-[ [/li]
-
I don't have a test box, only a live machine.
-
-
It's ok, not every ticket applies to every person. Even just looking at the list and seeing that none of them apply to you in a testable way is helpful.
What we're looking for there is just some feedback from people who have seen those issues to let us know if they have been fixed.
-
[Shamelessly copied from the same post I did for 2.0]
Right now there are 75 tickets in "feedback" state for 2.1. That is, they are supposed to be fixed but we are waiting on feedback from users to determine if issues can really be closed.These tickets can be seen here:
http://redmine.pfsense.org/projects/pfsense/issues?query_id=28It would help speed up the development process if everyone would go through the list and test a few of the tickets.
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 close 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!
-
Do all the ones in Feedback have to be tested before release or move to RC1/2 or are there a particular few that needs verification? If so, please let us know which few. We can tackle them first.
-
Before a release, they should all (ideally) be resolved.
Particular focus would be on tickets marked as feedback recently (the last few weeks) since those were the most recent changes.
Older ones are more likely to actually be working OK but it would still be nice to have confirmation where possible.
Feedback tickets wouldn't necessarily hold back an RC release, since some people would wait for a new RC to test again.
-
I have done a few. Testing another one tonight ( http://redmine.pfsense.org/issues/2633 ), will update the ticket when I'm done.
Actually, Jim. This one I've tested is still open.. can probably be marked as complete.
http://redmine.pfsense.org/issues/3001Josh.
-
This ticket is fixed, you can close Bug #3062.
-
Is it possible to get #3064 looked at for 2.1? Though it’s really an underlying FreeBSD issue, they haven’t responded to my PR to get the fix backported to 8.3 :(
-
These tickets can be seen here:
http://redmine.pfsense.org/projects/pfsense/issues?query_id=28Well, there're no tickets anymore…
So the 2.1 Release is soon done now?Peter
-
Seems so - But not to fear. We can start a new thread and nag the devs incessantly about things we want in 2.2
