mysql-native release v3.0.3
Steven Schveighoffer
schveiguy at gmail.com
Tue Sep 14 12:00:45 UTC 2021
On 9/14/21 5:16 AM, surlymoor wrote:
> On Tuesday, 14 September 2021 at 06:14:44 UTC, bauss wrote:
>> See:
>> https://github.com/mysql-d/mysql-native/pull/214#issuecomment-874692651
>
> Thanks! Should've checked for recent activity before posting, it seems.
> Last I knew, Steven said there was some heavy-lifting to be done before
> merging, so I hope it hasn't been too burdensome.
No worries, I am carving out time here and there to work on it.
There are 2 heavy lifts here, both of which I think need to be done
before a release.
1. I need to "rebase" the code. And by rebase, I mean create a new
branch based on the existing master, and implement the changes again. So
much of the safe branch involves the tests, and the tests have been
completely factored out into an integration project, so a true rebase
would be painful and likely wrong.
2. The documentation generation absolutely has to work. This is going to
be a very different experience in terms of how you use the library for
the immediate future. So I need the docs to reflect how to use this
library, and have them automatically build and publish. I plan to use
github actions for this, I just have to find the time to do it.
For certain, the safe branch is top priority for this project. I have so
many warnings in vibe that say unsafety is deprecated, please use a safe
function, and I can't because all of my backend db code is unsafe. So I
cringe and occasionally sprinkle @trusted tags here or there, but I want
to definitely move to all @safe code (where possible).
-Steve
More information about the Digitalmars-d-announce
mailing list