-
Notifications
You must be signed in to change notification settings - Fork 27
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
New release v2.0.0-beta.3 or v2.0.0 #192
Comments
We can definitely release a beta3 any time, but for 2.0.0-final I'd like to have #97 since it's a backwards incompatible change. I couldn't immediately find the branch where I've worked on it. IIRC it was more involved than expected. I can look into it towards the end of the week. We should also upgrade the Go version and any upgradeable module in go.mod, but that's of course easy. |
@magnusbaeck #97 has landed, should we release a beta3 now for? |
Yes! I'm off-grid until Monday night, but feel free to do it if you don't want to wait. |
No rush, I am now OOO until begin of August. |
I am back again. I suggest to get #206 and #207 merged and then release beta.3, what do you think @magnusbaeck? |
Yes, that's exactly the idea. I was just about to push the tag when I discovered that |
Beta 3 is available now. I have an in-progress commit that shapes up README.md quite bit that I'd like to get into 2.0.0 final; see the readme branch. There's still some work to do but I think it's in decent shape. |
@magnusbaeck I have not followed the most recent tickets, but I feel like there have not been many reports of (severe) issues since v2.0.0-beta.2 (Oct 2, 2021) so maybe we should consider releasing v2.0.0 or at least a v2.0.0-beta3 containing the latest fixes for the recent Logstash versions. What do you think?
The text was updated successfully, but these errors were encountered: