01:21 <zbret> Hello

01:42 <Squidly_> Is there a best practice for declaring an obsolete gem deprecated? or is simply best to ignore it and hope it will go away?

16:54 <dentarg> when I do gem install github_changelog_generator it tries to install 1.11.0 which was yanked yesterday https://rubygems.org/gems/github_changelog_generator/versions, is that due to some caching going on with rubygems index?

20:01 <SquidlyJones> General Question: Are there best practices for deprecating an old gem in rubygems.org?

20:19 <pipework> SquidlyJones: Entirely?

20:20 <pipework> Yank all versions, push new version that is major version of normal with no code that just depends on a new suggestion, perhaps, but also updates the gemspec to describe the deprecation and who to get a hold of. Maybe mention a forum/googlegroup/librelist and set that to the author email and name?

20:20 <pipework> Or just leave all versions.

20:21 <pipework> No need to yank unless there's a reason you want them all gone.

20:23 <SquidlyJones> No I just want to send the signal that the gem's time is done.

20:24 <SquidlyJones> So far I just release a new version with the word [Deprecated] in the description.

20:32 <SquidlyJones> In any event, it seems that I can continue as before as there seem to be no objections. Thanks