Skip to content
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

preparing new v3 release #368

Closed
11 of 12 tasks
jkralik opened this issue Jul 30, 2022 · 4 comments · Fixed by #405
Closed
11 of 12 tasks

preparing new v3 release #368

jkralik opened this issue Jul 30, 2022 · 4 comments · Fixed by #405
Assignees

Comments

@jkralik
Copy link
Member

jkralik commented Jul 30, 2022

v3 main branch

https://github.com/plgd-dev/go-coap/tree/v3

Features:

Optional features:

Release date

2022.10

@jkralik
Copy link
Member Author

jkralik commented Jul 30, 2022

@beriberikix @tim-golioth As we prepare to release version 3, I would like to ask if you have any changes from the API side that need to be made, or if you would be able to contribute some changes, for example #313.

@tim-golioth
Copy link
Collaborator

I don't have anything at the moment. Only thing I had recently was #341 , but that has been approved/merged already. (Note on this one: this PR has a bug in that it looks like the actual code being returned is 4.17, not 4.29. I have a ticket in our backlog to fix this, which I'll be sure to open a PR here as well. Should be able to get it fixed this week.)

Let me take a look at #313 and see what's involved. Since this release is targeting 2022.10, it might be something I can take on.

@tim-golioth
Copy link
Collaborator

follow up about the 4.17/4.29 issue: this is a no-op. it was specific to our internal code. nothing related to go-coap.

@tim-golioth
Copy link
Collaborator

@jkralik i don't have the bandwidth to take on #313 at the moment. i am interested in the topic, so maybe i can find time in q4 to work on this. if this is urgent, maybe there is someone else who can work on it in the meantime.

@jkralik jkralik mentioned this issue Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants