Closed jasonabele closed 10 years ago
Jason A: What's an appropriate way to review this so we can move it forward?
First, 3.10.7 is out, and I think it fixes an issue I was having, so I want to confirm that first and then maybe aim at 3.10.7 instead of 3.10.3
Also, I propose running the new master candidate branch through our various jenkins tests ... comparing the results and making a decision to roll forward based on that. How about I show that comparison at tomorrow's releases meeting?
Sounds good to me.
On Thu, Aug 15, 2013 at 12:44 PM, jasonabele notifications@github.comwrote:
First, 3.10.7 is out, and I think it fixes an issue I was having, so I want to confirm that first and then maybe aim at 3.10.7 instead of 3.10.3
Also, I propose running the new master candidate branch through our various jenkins tests ... comparing the results and making a decision to roll forward based on that. How about I show that comparison at tomorrow's releases meeting?
— Reply to this email directly or view it on GitHubhttps://github.com/cozybit/open80211s/pull/30#issuecomment-22724722 .
abandoned in favor of #35
I have been using 3.10.x backported on my dev box for a while now.
I propose its time to move open80211s master forward from 3.6 to 3.10
The usual suspect patches from master have been rebased onto v3.10.3 in this request and I would expect us to force push this branch to master rather than merge, as it is definitely not a fast-forward.