Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2019.10 release planning #486

Closed
10 of 17 tasks
vit9696 opened this issue Sep 10, 2019 · 9 comments
Closed
10 of 17 tasks

2019.10 release planning #486

vit9696 opened this issue Sep 10, 2019 · 9 comments

Comments

@vit9696
Copy link
Contributor

vit9696 commented Sep 10, 2019

We want a relatively small bugfix release in October as new macOS is arriving shortly and it is not a good idea to break stuff right away.

@vit9696 vit9696 pinned this issue Sep 10, 2019
@vit9696 vit9696 changed the title 2010.10 release planning 2019.10 release planning Sep 10, 2019
@Sniki
Copy link

Sniki commented Sep 20, 2019

It would be also nice to potentially include first release of Acidanthera/BrcmPatchRAM as it will be the Catalina release time and thousands of people will be affected with non-working Bluetooth.

Im glad you guys took over this project.

Respect for all of you.

@vit9696
Copy link
Contributor Author

vit9696 commented Sep 20, 2019

@Sniki, yeah, though it is mostly a formality, as we have not finished the migration yet. Recently we had a talk with @headkaze, and thought that it would be reasonable to work on this kext altogether on Acidanthera basis.

@mhaeuser
Copy link
Member

mhaeuser commented Sep 26, 2019

Required OpenCore documentation updates:

@DuIslingr
Copy link

DuIslingr commented Sep 27, 2019

@Download-Fritz that first thing is interesting because in QEMU I was not able to boot the OpenCore.efi directly. I had to use BOOTx64 to boot opencore. It said the OpenCore.efi was not an application when I tried. I tried this on a self built 0.5.0 build in August. Have not yet tried the newer official release on the OpenCorePkg releases.

@mhaeuser
Copy link
Member

@Dulslingr That is because OpenCore is not an application, it's a driver loaded with the "load" command.

@DuIslingr
Copy link

Oh ok that makes sense.

@vit9696
Copy link
Contributor Author

vit9696 commented Oct 7, 2019

So, current blockers are

@vandroiy2013 vandroiy2013 unpinned this issue Oct 8, 2019
@vit9696 vit9696 mentioned this issue Oct 8, 2019
9 tasks
@balthild
Copy link

Before the release of acidanthera/BrcmPatchRAM, can I use RehabMan/OS-X-BrcmPatchRAM with OpenCore?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

6 participants