-
Notifications
You must be signed in to change notification settings - Fork 106
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
Create a 0.4.x branch #122
Labels
Comments
No objection. Please tell me if your current privileges do not allow you to do this. |
Any progress on this one? |
Hi @clausecker! I have been really far away form nfc stuff for years, and that library really deserve some love! I invited you as a collaborator to the project, and hope you will accept it and help bring libfreefare where it makes sense 😉 Thank you! |
Hi @smortex. I'll look into what I can do. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should consider creating a 0.4.x branch with backported security fixes.
The 0.4.x branch would allow existing applications that require the original API to continue to work, but still be able to receive security updates and changes that don't break the established 0.4.x API/ABI.
I'd recommend branching at faac4ae (See #46), since that is the last commit before breaking API changes occur.
Maintenance of the 0.4.x branch would be on a best-effort basis.
The text was updated successfully, but these errors were encountered: