[returningfory2]

FYI, I think that as of this comment you don't understand what the maintainer was being asked to do. There is nothing in the code to fix. There is no dependency to be updated. Forking and doing whatever isn't what's needed. The person is just asking the person to tag a new release. The requester can't do this themselves.

[justinclift]

> The person is just asking the person to tag a new release.

Just to point out, making a new release can be a fairly involved "all day" process depending on what supporting stuff needs doing. eg blog post(s), getting people to manually sign things, notifying other people, etc

Literally no idea if that's the case for this project, but it definitely is for some of the projects I'm on.

[returningfory2]

Yes for sure! And in fact the person clarified elsewhere on this thread that it would be multiple hours of work to create a new release (in which case I think they’ll asking for support is totally reasonable). But just from looking at the exchange on GitHub this is not clear.

[bugglebeetle]

More pointless semantics. So your claim is that there is absolutely nothing IBM can do to resolve this situation, with all their myriad resources, besides opening a GitHub issue and then using absurd, abusive language in follow-up emails? Okay.

[returningfory2]

On my GitHub repos creating a new release generally involves using GitHub’s new release UI, which only I can do because I’m the only one with permissions. If someone else wanted a new release on my repo, how can they do this without me doing it?

[bugglebeetle]

…fork the repo and build a release yourself?

[vsl]

They can use a master or specific commit checkout. Makes it more unreasonable, not less, to harass the maintainer.