> > if it doesn't end up in there, it doesn't end up in the release.
> And it won't. The team was getting pushback from the ROM preservationists themselves
> about last-minute changes to ROM sets. In this case, it missed the freeze cutoff
> date, and the fact that the ROM set changed means that it will not be cherry-picked
> for the release branch.
> I understand that this might be annoying to some users, but I'd rather annoy some
> users than annoy the people who actually provide ROM set distribution, and a rule
> that can't remain a rule for more than two releases can hardly even be called a rule.
Interestingly the 'rom preservationists' I talked to seemed to dislike the rule. Having an updated romset one day, only for it to instantly go out of date again the moment a release is made wasn't sitting well, especially not when the rom changes are the very things people want to try asap.
I'm not a fan either, while I can understand core feature freezes I don't think it benefits MAME to ship information that is known to be out of date (eg. I don't think the Biomechanical Toy redumps made it, and there's absolutely no reason to continue to ship out of date information there, benefits nobody) I'd consider that anti-preservation.
Also, a software list update was pushed into that branch the day before release, which seems to fly in the face of the rule.