I'm afraid you don't understand the problem with questions 7 and 8: informed answers would require in-depth knowledge, with a lot of critical awareness, of a large number of techniques that are described in hard to find primary sources and commonly misunderstood. So it might make sense to ask what practices one has heard about (and from what sources), or what people
say they are doing, but asking what a developer is actually doing is to a large extent ill-defined (e.g. how many untested emergency fixes are enough to void a rigorous testing process? How many late night emergencies can fit in a 40-hours work week?) and it requires weeks of study.
As noted in other comments, there's also the issue of your assumptions; for example release cycles with a definite scale, while in reality there are nested or overlapping long and short cycles (from edit-compile-run to formally discussed tickets and other units of work to public releases and updates to grand rewritings and replacements): different practices apply to each cycle.