Is there any way to cut a new release off master?
Rails5 is almost done and there is no version that is compatible yet, but the master branch seems to be fine due to a couple things that were fixed since January. Using Rails, Sidekiq, and Sinatra (for the Sidekiq administration) is a common paradigm.
b264
All 10 comments
There will be a release as soon as I can, until then feel free to use master.
zzak
on 22 Jun 2016
A 2.0.0-beta1 release that bundle update can upgrade would be better than folks using a commit sha on master or their own fork, in my opinion. The beta would imply it's not done yet while still allowing a successful gemfile resolution by bundler.
b264
on 22 Jun 2016
I will consider cutting a pre-release, thanks.
zzak
on 23 Jun 2016
b264
on 24 Jun 2016
b264
on 24 Jun 2016
b264
on 24 Jun 2016
b264
on 24 Jun 2016
@zzak thoughts on cutting a pre-release?
ericboehs
on 5 Jul 2016
@ericboehs Thanks, I'm still considering
zzak
on 6 Jul 2016
For anyone coming back to this, the reason for not releasing yet is because I'm waiting to merge stable sinatra-contrib and rack-protection gems into the repo.
However, there is a blocking release on contrib and working through the remaining issues before I can do that.
Any help there is appreciated to speed up the release :bow:
No, I don't think I want to release before that is done, even a pre-release because I explicitly said that sinatra-contrib will be a first-class citizen.
Sorry for the delay, but you're free to use master until that work is done.
If you run into any issues please report them, but I'm not going to consider a release only to change one line in your Gemfile.
zzak
on 7 Jul 2016
Related issues
namusyaka
路
5Comments
polyglot0027
路
3Comments
namusyaka
路
3Comments
paulmenzel
路
4Comments
GCorbel
路
7Comments
Most helpful comment
I will consider cutting a pre-release, thanks.