In the interest of progressing 7.10 and helping the developers I was thinking of searching through all the tickets to see what could be cleaned up.  I started looking and soon realized that I don't have a clue on some of them since either a) I don't have the hardware or b) haven't seen that particular problem before.

Here's one such example that I can relate to since I have a few DG834Gv2's and have never seen this problem.  nabcore, we've been through a few new kernels since the last post.  Is it still a problem?  You've done some fantastic testing for the project nabcore, I don't mean to single you out, but you get the idea.

So instead of going through all the tickets myself, why not help out the devs and everyone take part in researching them a little more.  I for one think OpenWrt is by far the best embedded distro out there.  It's "use only the packages you need" and "CLI only" approach has helped me learn more and more about the inner workings of Linux.

ar7-2.6 is nearly stable and it's about time it's included in a non-svn release of Kamikaze.
I think there needs to be some focus put on this ticket and we can all help out: https://dev.openwrt.org/ticket/2024

Still not sure why 7.09 still has active tickets....shouldn't they all be moved over to 7.10?

Hi KillaB,

With respect to https://dev.openwrt.org/ticket/2332 , I've not seen it in a while, hence it can be closed. As an aside, I don't like closing bugs because they've not been seen in a while. I subscribe to the concept of causality; every problem has a cause and when a bug is closed because of its age, it's never known if its cause was actually solved. Conversely, I am aware that this is a real world situation and sometimes "things just need to be done".

Secondly... I have a quite a few bugs in the database and I think the major issue I've found with the AR7 section of the OpenWrt project is that of apathy. In some bugs, I've actually offered a solution with in the ticket:

https://dev.openwrt.org/ticket/3222

As for others, they are just epic issues that never seem quite solved and never see an end in sight:

https://dev.openwrt.org/ticket/3124
https://dev.openwrt.org/ticket/3047

And then other bugs just never get picked up:

https://dev.openwrt.org/ticket/3120
https://dev.openwrt.org/ticket/2999
https://dev.openwrt.org/ticket/2988
https://dev.openwrt.org/ticket/2555
https://dev.openwrt.org/ticket/2378

Some of these could be closed with, "not seeing any more, hence close it", but I rarely run the latest trunk any more since I sick of breakage. I'm trying to make some progress with acx-mac80211, both in being a test bed and providing patches back to the main acx-mac80211 devs. I cannot do this if my development platform works one day and then does not the following day: the move from 2.6.23 to .24 caused two months of issues with the ethernet support. If I'm messing around with a regression issue, it takes time away from helping some new along and I think getting the wireless to work on this device is a good target.

Returning to the point at hand, it may be worth triaging bugs on whether they actually hold up the next release.