-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for NXP KW2xD MCU #2942
Comments
by Mark Linkmeyer: Hi Johann Fischer , do you expect to get this story implemented in time for the upcoming 1.7 release? It would need to be implemented, code reviewed, and merged before the 1.7 feature merge window closes on Feb 1st. Thx. |
by Johann Fischer: Hi Mark Linkmeyer , I think it's possible, I'll look over it next week when I'm back in the office. |
by Mark Linkmeyer: Hi Johann Fischer , I know it's only Tuesday :-), but I was wondering if you've had a chance yet to determine if this is feasible to get done in time for 1.7? If you haven't, sorry, I don't mean to rush you. More importantly right now, I was wondering, since you submitted this story, could you set the priority field? It currently has undecided priority and because of that I'm not sure how closely I should be tracking/monitoring it. Please use the following when setting it: Highest = Must-Have in 1.7, High = Should-Have in 1.7, or Medium = Nice-to-Have in 1.7. Or, if Maureen Helm is the right person to set it, that's fine too. Thanks! |
by Johann Fischer: Hi Mark Linkmeyer , I would change it to v.1.8.0 or change to lower priority, it's too tight. |
by Mark Linkmeyer: Johann Fischer , in cleaning up issues in preparation of the move to GitHub issues, I cleared the FixVersion field for this story because it was set to 1.8 and 1.8 was already released. If you know when it is now planned to be released, please set the FixVersion field accordingly. |
Blocks GH-2943 |
Fixed by #845 |
Reported by Johann Fischer:
Add support for the KW2xD Kinetis Wireless Radio MCU (-KW21D256-, KW22D512, KW24D512)
(Imported from Jira ZEP-1471)
The text was updated successfully, but these errors were encountered: