-
Notifications
You must be signed in to change notification settings - Fork 633
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? #656
Comments
Wait up! There are some commits in |
I understand the pending issues but the last release is almost 1 year old now and there hasn't been any movement on those issues since May/June 😕... |
If it helps, you can just specify the commit you need in your Gemfile: gem 'pundit', git: 'https://github.com/varvet/pundit.git', ref: '504b86a' |
Of course! I did it back in May, but I hope you'll agree that's not a long-term solution 😅 |
I'm looking forward for a new release, specially because of https://github.com/varvet/pundit/blob/master/lib/pundit.rb#L24-L41. Any plans for 2020? |
If anyone search for alternative simillar to Pundit: |
Any news in here? It doesn't look good with the last meaningful commit 17 months ago. |
@kindell @olleolleolle @dgmstuart What are the long term plans for Pundit? I was planning on using Pundit as the primary example of Authorization combined with Sorcery as the Authentication, but it is a bit concerning if the release cadence is looking unhealthy. |
Hi! I can't speak for the other maintainers, but I can give you some information from Varvet. This is all preliminary as we're still figuring things out at Varvet, and I can't run this post by @kindell or @dgmstuart since they're both (me too, really) on ~4-week swedish vacation and are off-grid right now. Please keep some spare oversight in hand while reading this. That said, I just noticed this issue and I figured a vague reply is better than none. The short answer is that we at Varvet have no intention of abandoning Pundit. It's likely that we'll continue spending resources on Pundit, and if that turns out to not be an alternative we are probably looking at finding a new maintainer. The long answer is that recently (~mars 2020) Varvet as a company underwent a significant restart. We're a much smaller shop now, so @dgmstuart and I started doing inventory of our OSS projects and trying to figure out what to do with all of them. Most of the time until now has been spent on building up and getting to know the new company we just rebooted, and our public communications suffered. I'm sorry. I can't do much right at this moment, but I can promise I'll take a closer look together with @dgmstuart late august when we're both back from vacation and are on-grid again. |
Agreed. That said, it shouldn't keep us from making a new release. We'll revert the change in master in order to make a new release soon (tm). As for error reasons/messages that discussion can move to #654 for now. |
This reverts commit 6be4621, reversing changes made to 872ed68. Reverting this because it's blocking us from making a new release, see: #656 (comment)
Hi again! The new release is out and available on Rubygems. |
Latest release was August 2019, and since then there have been lots of commits in
master
.Would the team consider releasing a new version with all the new fixes/features?
The text was updated successfully, but these errors were encountered: