You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The last tag/release was Sept. of 2020, and there have been a fair number of commits to the project since then, most notably the fix to a critical bug reported in #135
Would it be possible to create a new tag/release that reflects the current state of the codebase?
This is particularly helpful for packaged installs, where the maintainers key off of new releases to create new versions of a package.
The last tag/release was Sept. of 2020, and there have been a fair number of commits to the project since then, most notably the fix to a critical bug reported in #135
Would it be possible to create a new tag/release that reflects the current state of the codebase?
This is particularly helpful for packaged installs, where the maintainers key off of new releases to create new versions of a package.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063730 for reference, the Debian package suffers from #135 , and I think it would be a lot easier to get an updated package if there was a 2.6.1 release of this software.
The text was updated successfully, but these errors were encountered: