Repository not in sync with upstream Ruby master

[stomar]

There are both commits in ruby-core that are not synced to this repo and vice versa.

E.g. (not an exhaustive list, only the first two commits I noticed):

• only in Ruby repo: 048f797 2019-12-22 [ruby/prime] Bump version
• only here: 55dda6a 2019-08-11 Fix Prime.include? [bug fix not shipped with 2.7.0]

(Of course, my recent commits are not expected to be synced yet.)

Where does development happen? What's the process for syncing?

[stomar]

@hsbt, @yugui

[marcandre]

Oh... I'm sorry about this. I thought it was done somewhat automatically or regularly 😢

I should have doubled-checked.

I'll fix that.

[marcandre]

Actually @hsbt weren't they was supposed to be sync'ed? That's what I understood from ruby-core:87942. What should can I do to help?

[marcandre]

I think it would be best to rewrite this repo's history to place the version commit in the right position in the history, and bump the current version to 0.1.2 and release it.
Objections?

[headius]

It doesn't appear any prime gem has been released other than the empty 0.0.1, yes? I'm trying to set up JRuby's 2.6 branch to pull the prime gem, but there's nothing there!

[headius]

Closing the loop: the "prime" gem name is still reserved by someone else, so nothing has been released there. For now I'm restoring the in-repository copy of prime for JRuby.

[marcandre]

I hope to have some time tomorrow to see what I can do on my end.

[headius]

@marcandre See also this thread: https://twitter.com/headius/status/1235632713291317248