[Issue 16699] [REG 2.070] stack corruption with scope(exit)

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16699

--- Comment #19 from Ketmar Dark <ketmar at ketmar.no-ip.org> ---
actually, i believe that no merges from stable to master should be done at all.
if hotfix is applicable to both branches, it should go to both branches, first
in master, and then, possibly with another PR, in stable. not the other way
around. if autotester is the blocker, then something should be done with
autotester. but in no way master aka "dev" should be behind stable in terms of
bugfixes.

all the new developement is done on master, so master should have all bugs
fixed first, so people won't spend time chasing the bug that may be fixed in
stable, but not merged to master yet. actually, i think that PRs against stable
should be rejected if there is no equivalent PR against master, or link to
already existing PR that fixed the bug.

sure, this may add some burden on devs, but i believe that it is better and
helthier way to do developement work. for now it is unclear which branch has
bug fixed, for example. it is marked as fixed in bugzilla? ok, i'll go with my
dev work the... oh, wait! it is not fixed in master! so i have to rebase my
work on stab... oh, wait! we aren't doing dev against stable! ok, i'll
cherry-pick it myse... oh, wait, merge arrived! ah, fsck all that mess, i
already lost the motivation.

--