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.

Sign up for GitHub

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

Jump to bottom

Versioning libbpfgo #39

Closed
yanivagman opened this issue Jul 22, 2021 · 0 comments
Closed

Versioning libbpfgo #39

yanivagman opened this issue Jul 22, 2021 · 0 comments

Comments

@yanivagman
Copy link
Collaborator

yanivagman commented Jul 22, 2021 •
edited
Loading

As libbpfgo depends on libbpf and there are features in libbpfgo that require some minimal version of libbpf, we should add the version of libbpf to be part of the version of libbpfgo.
This can be, for example:
v0.2-libbpf_0.4
grantseltzer added a commit that referenced this issue Aug 2, 2021
@grantseltzer
Add section in README about release versioning
4d60525 
This describes @yanivagman's idea in #39.  I would immediately follow up this PR merge with the cutting of a new release based on the scheme described here.
@grantseltzer grantseltzer mentioned this issue Aug 2, 2021
Merged
grantseltzer added a commit that referenced this issue Aug 3, 2021
@grantseltzer
Add section in README about release versioning (#47)
c500b62 
* Add section in README about release versioning

This describes @yanivagman's idea in #39.  I would immediately follow up this PR merge with the cutting of a new release based on the scheme described here.

Signed-off-by: grantseltzer <grantseltzer@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yanivagman