So far I know of at least three fixes which should probably go into 2.0: * my fix for the configure stack-protector checks on MacOSX * MST's pull request updating the ACPI test blobs * MST says we need to update the hex files for ACPI too (otherwise you get a different ACPI blob depending on whether your build system had iasl or not, if I understand correctly)
Are there any others? So we have two choices: (A) get those fixes into git today, and tag an rc3; that would then need some testing time and presumably we'd hope to tag it as the 2.0 release on Monday or Tuesday next week (B) say that the above are not worth fixing in 2.0 proper and plan to do a 2.0.1 in a few weeks with the above plus any other breakage that people find. Opinions? thanks -- PMM