Version 0.6.7 has been in the tree for a little over a month without any bugreports, so I think it's safe to keyword it stable. This would allow me to finally get rid of the old 0.5.x version, since 0.6.x is the stable branch now.
amd64/x86 stable
This version breaks madwifi-ng in master mode and ath5k isn't able to do master mode yet. 0.6.8 is broken too. On startup they spit a couple "ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument" errors and even though it starts it doesn't work as expected, be it with a new config based on the template or the previous config i used with 0.5.10. Also why stabilize an upstream development branch?
To elaborate on that, 0.6.x starting from 0.6.8 is considered stable, but 0.6.7 isn't and there were changes between both.
Please report another bug about your issue (assign it to me), and please include the output of emerge --info and what version of madwifi-ng, linux-headers and kernel you are using. As for marking 0.6.7 stable, I see your point. I'll close this bug, and ~arch it again, since I mixed 0.6.7 and 0.6.8 regarding being stable.
Bug #260377, seems i can't reassign even being an ex-dev.
