-
Notifications
You must be signed in to change notification settings - Fork 132
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 of current branch? #73
Comments
@sleinen Can you do a new release? |
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. Further, use a pidfile. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. Further, use a pidfile. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is happening [0]. So fork the repository and create a new release. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using yyyy-mm-dd of the commit. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. In addition, add necessary "PKG_FIXUP" and "PKG_REMOVE_FILES" to allow compile the new version. Also add enable "PKG_BUILD_PARALLEL". Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
This is a quite reference spamming. :) |
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. In addition, add necessary "PKG_FIXUP" and "PKG_REMOVE_FILES" to allow compile the new version. Also add enable "PKG_BUILD_PARALLEL". Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. In addition, add necessary "PKG_FIXUP" and "PKG_REMOVE_FILES" to allow compile the new version. Also add enable "PKG_BUILD_PARALLEL". Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]> (cherry picked from commit a6d7ed4)
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. In addition, add necessary "PKG_FIXUP" and "PKG_REMOVE_FILES" to allow compile the new version. Also add enable "PKG_BUILD_PARALLEL". Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]> (cherry picked from commit a6d7ed4)
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. In addition, add necessary "PKG_FIXUP" and "PKG_REMOVE_FILES" to allow compile the new version. Also add enable "PKG_BUILD_PARALLEL". Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. In addition, add necessary "PKG_FIXUP" and "PKG_REMOVE_FILES" to allow compile the new version. Also add enable "PKG_BUILD_PARALLEL". Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. In addition, add necessary "PKG_FIXUP" and "PKG_REMOVE_FILES" to allow compile the new version. Also add enable "PKG_BUILD_PARALLEL". Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]>
The newest master branch has important fixes. However, no new release is published [0]. Switch to git and update to latest master commit. This introduces new version scheme by using YYYY-MM-DD of the commit. In addition, add necessary "PKG_FIXUP" and "PKG_REMOVE_FILES" to allow compile the new version. Also add enable "PKG_BUILD_PARALLEL". Further, use a pidfile and remove outdated patches. sleinen/samplicator#73 Signed-off-by: Nick Hainke <[email protected]> (cherry picked from commit a6d7ed4)
@PolynomialDivision noticed you are using this project under openwrt and using master instead of the 1.3.6 release. What are the big differences from master to 1.3.6 in terms of bug fixing you are mentioning? |
Why was there never a release of current master branch?
The text was updated successfully, but these errors were encountered: