4.0 Release Timeline (?)

[fxfitz]

Hi all! Curious if you guys have a timeline for a full 4.0 release? What's blocking that?

[vivianezw]

I think Cohen would say that current release is working sufficiently well. ;-)

To throw some things in:

• there are still some open glitches and bugs, some I cannot fix.
• some I can fix, but didn't. ...It never seems to be so urgent...
• Is signing before the final deadline of MS even a solution? This won't hold forever.
• Should we maybe take another way, e.g., why not become a KDU supporting driver? That would allow now and in future to run under modern Win10 with secure boot and normal security enabled (except Core Isolation), and we could still fix bugs and release updates without worrying. Is it realistic to assume that, knowing there are already bugs that currently cannot be fixed, this driver will hold for at least 5 years? Testsigning the driver is not a solution for most people.

Scudette can decide that. I'm also fine with 'current release working sufficiently well'. No work. ;)

[scudette]

I think the only bug left to fix is that the user space code is not removing the driver file under some situations. I can take a look at it. I am also happy to just call this a release instead of a release candidate (rc) Thanks Mike

…

On Wed, Feb 3, 2021, 8:01 PM Viviane ***@***.***> wrote: I think Cohen would say that current release is working sufficiently well. ;-) To throw some things in: - there are still some open glitches and bugs, some I cannot fix. - some I can fix, but didn't. ...It never seems to be so urgent... - Is signing before the final deadline of MS even a solution? This won't hold forever. - Should we maybe take another way, e.g., why not become a KDU supporting driver? That would allow now and in future to run under modern Win10 with secure boot and normal security enabled (except Core Isolation), and we could still fix bugs and release updates without worrying. Is it realistic to assume that, knowing there are already bugs that *currently* cannot be fixed, this driver will hold for at least 5 years? Testsigning the driver is not a solution for most people. Scudette can decide that. I'm also fine with 'current release working sufficiently well'. No work. ;) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5NRIVXUVT4SZQIJ6AJT43S5ENHLANCNFSM4W7DQZ6A> .

[fxfitz]

Nice! Any way we could get an official release 4.0 release cut here https://github.com/Velocidex/WinPmem/releases ?

[scudette]

Sure. I will make one. Just trying to fix the last bug about the deleting the driver temp file. It seems to leave that behind Thanks Mike

…

On Thu, Feb 4, 2021, 02:26 Fran Fitzpatrick ***@***.***> wrote: Nice! Any way we could get an official release 4.0 release cut here https://github.com/Velocidex/WinPmem/releases ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5NRISPQE34FEBC57IFEFTS5F2LHANCNFSM4W7DQZ6A> .

[fxfitz]

Awesome, thanks! I'll keep an eye out for it.

[fxfitz]

@scudette Any progress on that official release?

[utkonos]

Is there a planned release based on the bugfix PR #41 ?

Also, it's totally understandable if there is no release and no further planned releases. If that's the case, can you provide a set of instructions for the building / signing process?

If not, that's ok too. I understand that open source is totally a volunteer activity.