On Thu, Apr 10, 2014 at 01:24:51PM +0200, Alexander Graf wrote: > > On 10.04.14 13:17, Peter Maydell wrote: > >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? > > I think the best way forward is to do both. Do an rc3 with _only_ > those patches. Wait until Tuesday and do the final GA tag there. > > Then schedule a 2.0.1 in a few weeks. There will be bug fixes. > > And don't apply last-minute fixes from mst in the future :). > > > Alex
Sorry about that. Though my last minute patches didn't actually break any stuff, they just weren't complete :) -- MST
