@weshatheleopard jeweler uses itself to release, so that should be all familiar
the only thing I'd suggest is to batch merges & releases. ie, merge the rubby 2.3 branch, and release it
in the past, found that too much unreleased code in master makes it hard to merge & release other things
also: circumvents people asking "hey, can someone release this?" after a mrege
Yeah, that's how I do it anyway.
I have taken over maintenance of Jeweler, and have updated it to work with the latest Ruby. Earlier I forked it and created https://github.com/flajann2/juwelier which I will be adding new features to. Eventually I will merge both into one.
I recommend using Juweilier for new projects. You can also convert Jeweler gems over to Juweilier as documented in the README.
I have closed a number of the really old issues, circa 2010. If anything of those are still a concern, please reopen or resubmit them. Thanks.