Thread overview
mysql-native release v3.0.3
Sep 14
surlymoor
Sep 14
bauss
Sep 14
surlymoor
Sep 15
surlymoor
6 days ago
surlymoor
September 11

I just tagged a new release. This fixes a couple of minor issues. See the Changelog for details.

-Steve

September 14

On Saturday, 11 September 2021 at 16:38:28 UTC, Steven Schveighoffer wrote:

>

I just tagged a new release. This fixes a couple of minor issues. See the Changelog for details.

-Steve

Hey Steve, thank you for the work you're putting into this. Is there anything that needs to be done to expedite the @safe update's arrival, or is it just a lack of time?

September 14

On Tuesday, 14 September 2021 at 03:23:12 UTC, surlymoor wrote:

>

On Saturday, 11 September 2021 at 16:38:28 UTC, Steven Schveighoffer wrote:

>

I just tagged a new release. This fixes a couple of minor issues. See the Changelog for details.

-Steve

Hey Steve, thank you for the work you're putting into this. Is there anything that needs to be done to expedite the @safe update's arrival, or is it just a lack of time?

See: https://github.com/mysql-d/mysql-native/pull/214#issuecomment-874692651

September 14

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.

September 14

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

September 15

On Tuesday, 14 September 2021 at 12:00:45 UTC, Steven Schveighoffer wrote:

>

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.

[...]

Appreciate the information, and love that you're focused on the documentation aspect. Wish I or somebody else could help with that latter item at least, but I'm pretty useless. Regardless, hope all goes well.

6 days ago

On 9/14/21 8:14 PM, surlymoor wrote:

>

On Tuesday, 14 September 2021 at 12:00:45 UTC, Steven Schveighoffer wrote:

>

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.

[...]

Appreciate the information, and love that you're focused on the documentation aspect. Wish I or somebody else could help with that latter item at least, but I'm pretty useless. Regardless, hope all goes well.

Maybe you could take a look at how Mathias Lang does it here and see if it's easy to do something similar for mysql-native.

I really would appreciate any help on getting the docs building! I know the previous versions used ddox (and a custom build of it at that), but I am not locked into that at all, and am willing for ANY documentation that is functional to replace it. It's critical to me that this is automatic, as I've published docs manually for other projects, I notice the result is, it doesn't get done.

-Steve

6 days ago

On Wednesday, 15 September 2021 at 13:42:39 UTC, Steven Schveighoffer wrote:

>

Maybe you could take a look at how Mathias Lang does it here and see if it's easy to do something similar for mysql-native.

I really would appreciate any help on getting the docs building! I know the previous versions used ddox (and a custom build of it at that), but I am not locked into that at all, and am willing for ANY documentation that is functional to replace it. It's critical to me that this is automatic, as I've published docs manually for other projects, I notice the result is, it doesn't get done.

-Steve

I tested a setup out, and it seemingly works. Will make a PR during night's reign.