-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Release BeEF version 0.5.1.0 #2039
Comments
Sounds like a good idea. There seems to be some defect tags that should be fixed before the new release though. Let's get them fixed as soon as possible. |
Heya, I'll close that other issue. I think we should a release sooner rather than later. What has been the process for this? My versioning was wrong it should be @bcoles suggestion |
Tag a new release using the GitHub ui or
The versioning is a bit messed up. The most recent release is the vaguely named |
hey all lets put a target date for next Tuesday to create this release. I'll start to put together a list of all the merges that has happened. |
hey, list of fixes for this release Added libcurl4-openssl-dev to apt command #1807 |
@wheatley Looks good, that makes it more apparent that the release is severely needed. Are you fine to create the pull request to change the version? |
For reference, here's the diff since v0.5.0.0: |
I'm going to create a release branch to update the appropriate areas. why do we use
|
The versioning is kind of silly. BeEF is perpetually alpha software (and thus "alpha" is implied). I don't remember what the original intention was, but many years ago we switched to adding the |
Taking a look at the previous releases, they all take the form of:
|
We've released this version. |
A lot of things have been fixed in the last year.
It is probably time for a new point release.
@jcrew99
The text was updated successfully, but these errors were encountered: