-
Notifications
You must be signed in to change notification settings - Fork 691
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
Plan for new release? #533
Comments
I believe we've mostly focused on v2, though that effort has unfortunately stalled somewhat. I don't know if we plan on making another release for v1. What do you think @bwplotka? |
@johanbrandhorst What else is missing in v2 now? |
I'm frankly not sure v2 is ever going to happen at this point. I know Bartek has been very busy and just started a new job and I don't have any particular love for this project and generally recommend users don't use it. I might take some time to revamp this to be a "templates" project rather than something people use as a library, but I'm also busy with other things. I'm sorry to the users who are stuck in limbo, but as I said I generally recommend that instead of depending on this project as a library, you copy the interceptors you want to your own codebase and modify as necessary. There are too many specific use cases for a generic library like this, I think. |
looking at the number of "stars" and... just what I see in general, lots of people actually do use this project. If you don't plan to make new releases, maybe mark this project as deprecated then? I don't want to sound too snarky, it's just too much in limbo :) |
also I'm fine with "this is complete, we just accept bugfixes" that some projects do (like... logrus for example?), but as I linked above, there is actual memory leak fixed in master already that's not released, so that's an actual bug |
I actually wanted to sit down on v2 this week 🙃 Let's see if we can push this towards the finish line. The v2 is much more lightweight and allows writing your own "plugins/modules". In the mean time I will do "last" (or one of lasts) v1 releases with right comms, no harm in that. |
Thank you! |
The current release (v1.3.0) is quite old at this point
There was this issue, which hit me now, and is already solved in the master - #498 - but there might be more that I don't see.
Are there some plans for a new release?
The text was updated successfully, but these errors were encountered: