Conversation
|
I would also add #4020, it's a transparent evolution for 99.9% of users who dont need master/slave setup |
|
Also, I was waiting for your feedback on these 4 PR before making a new one to include 8.5 in the tests |
Normally I'd argue that I don't like changing API in a maintenance version, but we've already done that with #3999 so… Welp.
Thought you might've been. 😅 I'll keep things general in this public forum, but the last two weeks have been… a lot, for family reasons. We all just came back after two weeks out of town, and it wasn't for a vacation 😢 Will look at the outstanding PRs first, then, before turning to the release post. Can't promise a specific timeline what with catching up on year-end work stuff that was delayed, but fortunately we're all agreed that this is a chill project 😉 (I had a few minutes, so I looked at #4030 right after posting this. More to come when I have the cycles.) |
|
Ah, the last PR (#4020) got finished. Nice! Not marking it off yet; that empty checkbox is to remind me it has to go in the changelog still. Looks like this weekend will be release time, since I should be done with the next $work backlog by Friday and ready to write the blog post etc. 🙂 |
|
Added the last bit to the changelog here, and drafted release post at YOURLS/website#406 |
Hey @YOURLS/core team, I have an idea: Let's release our bugfixes and stuff from the last few months. We've been collecting patches since August :)
Starting in draft; if any of the following PRs are ready to merge within a week or so, they should be included:
yourls_get_db()#4020I'll work on a release blog post later this week, assuming I get through my $work backlog. But if I'm slower than expected, that's just more time for those PRs to ripen. 😁