hsbt will talk to nagachika (current Ruby 2.1 maintainer) about Heroku and hsbt’s request for a Ruby 2.1 bugfix release

hsbt has requested to be a submaintainer of 2.1 and needs nagachika’s approval

the current state of releasing is expensive because it requires machine and human resources. Ruby needs to be tested with many configurations. hsbt and ko1 will examine a CI env to assist in the release process.

we would like to release more often to handle critical bugs like a SEGV

need to figure out how to handle already backported commits on the release branch not in the hotfix

revert the commits (or find some way not to include them) that don’t apply
include them

matz says there’s no reason to distinguish hotfixes from a normal bugfix

hsbt: user comapny want to release patch release when it has critical bugs like SEGV. hsbt want to handle it as sub-maintainer.
ko1: heroku also want it.

up to nagachika about maintaining branch with 2 persons

hsbt reports to nagachika today’s discusion

for example immediate hotfix

hsbt collabolate to relase hotfix

naruse: current 2.1 branch already has some backports after 2.1.1. how handle them is the issue if we release 2.1.2 immediately. There’s some option (1) revert such commits (2) include them
naruse: if we choose hotfix model (release 2.1.1 with few ciritical fix), we need design new branching model