Textpattern 4.8.8 release flight plan #1720
Comments
|
Looking at the plans for the PHP 8.1.0 schedule, GA is planned to arrive November 25 2021. The issue queue for 4.8.8 is currently empty, so we have a few months to housekeep existing issues for some easy / effective wins. With that in mind, it seems pretty straightforward to tag 4.8.8 as a PHP 8.1 maintenance release, with a few bits of tidying as we go. Should a priority release be needed in the coming months before PHP 8.1 drops, we can defer any other PHP 8.1 changes to a 4.8.9 release. @Bloke @bloatware @philwareham Does that sound reasonable for now? Anything I've missed? |
|
Works for me. Any small wins from 4.9.0 we can bring forward? |
|
@Bloke If you have any insight into #1707 that might be an easy win. There are currently 20 issues without a milestone, so perhaps a couple of passes through those to housekeep might yield some gems. I'll take a nosey after some late lunch. |
|
There is a potential callback bug that needs investigating as part of this release. It's unconfirmed as yet, so no issue to track it at the moment. |
Not strictly from 4.9.0 milestone, but is there anything we can do with #1379 realistically? |
|
Note sure of the scope here – it may need an issue – but there's an RSS issue that has cropped up. It may be an easy win for 4.8.8: https://forum.textpattern.com/viewtopic.php?pid=331277#p331277 |
|
This is not really a core issue, but we can try to do something to accommodate hacky plugins. |
|
Raising this as an RFC since we're about two months from GA: do we need a beta release for 4.8.8? This is new territory for a patch release, but there's merit in doing the beta dance. There's some discussion about a beta in #1696 but I propose we have a thumbs up or thumbs down to gauge the consensus. Knowing what we do at the current time, and given this may be the last release on the 4.8 circuit, should we do one or more beta releases for 4.8.8? Thumbs up for 'Yes', thumbs down for 'No'. Paging @bloatware @Bloke @philwareham for input, and any readers with an opinion either way. Thank you. |
|
A beta seems prudent given the changeset. |
+9 |
|
Unless there's any objection, a beta seems like the way forward. Paging @bloatware & @philwareham – please sound off if you're against the idea for any reason. If no objection, I'll put a post in the forum, on the socials and a short .com blog post with our beta intentions. |
|
I'm fine with a beta, just thinking in two months it could get irrelevant. We are rarely keeping quiet when new ideas/requests come. |
Oh, definitely. +1. It's been a while since we had a beta release, and if it becomes a formality then that reinforces we were perhaps right to do it…but if there are issues uncovered, we may be able to address them easily for the GA release. Either way, there is some value to the end users (and us, because we get more practice with releases). |
I would expect a putative beta to be released ~ 2 weeks before final release, not much earlier and certainly not now. |
|
@phiw13 – Agreed, I updated OP with provisional guideline dates before your post above. Would appreciate your take on this, if appropriate. |
|
@bloatware - I think the penny just dropped when I re-read my comments and your reply, then @phiw13's comments. I should clarify: I was proposing a beta release around the time of PHP 8.1.0 GA, not now or imminently, then Textpattern 4.8.8 when we're happy it's playing nicely (let's say a few weeks later, assuming no major snags). |
|
@petecooper that would be great, thank you. I have tried, but failed to make it work. |
It appears to be a docs / procedural issue not code. |
|
I can run the 4.8.8 release unless there are any objections. Last and final boarding call, any reasons to NOT release today? |
|
#1774 appears to be OK, I followed the instructions from @jools-r and it worked just fine. Docs need some tidying but that's not a showstopper. The scope of #1775 is not fully clear to me, and that's a me problem, but the idea of relocating plugins from location A to location B on a patch release makes me a bit nervous. I could definitely see #1440 being a good contender for 4.9, which would take care of a bunch of stuff in the process. Plugin authors will need some notice on upcoming changes, too. That said, multisite is a neat feature that could be overhauled & marketed for the next release branch, especially if we can weaponise some evangelists who run multiple sites on the same server to actually use it in anger. |
|
Yeah, I'm not sure either. #1775 is kind of an oversight when we introduced the /textpattern/plugins directory. Arguably a bug because we're implying that your shared textpattern base install has to have the same plugins in all sites, since they're served from a central location. It's far better to have the plugin path cognisant of the constant so people can move the plugins out of the central area and into one of the per-site directories by simply (re)defining it in config.php. Adds flexibility. I can't see any backwards compatibility issue with @jools-r 's proposed patch |
Ah, OK - if it's that straightforward then perhaps it's an easy win. |
|
Issue queue is clear, time for us to get this sucker out, I think. Dibs unless @Bloke wants to run it. ETA: today (Monday, January 24th 2022) unless anyone says so. Paging @philwareham & @bloatware - happy to proceed? |
|
Yes, I'm happy to go. Will check Crowdin to see if any new translations need to be added to the Textpacks and Pophelp - then we can tag those repos for release. I'll also tag the themes and admin themes when you are ready to proceed. |
|
Yay. Let's do this thing. Happy for you to run it, thank you. We probably just want to mention in the release notes the potential backwards-compatibility issue with multi-site plugins dir. |
@Bloke - is that something you can do, please? Assume I'm a thick-o. |
|
Will start the release at 1300UTC, tools down 1245UTC latest, please and thanks. Gitter is open for any backchannel comms. |
|
Tools down, sirs. Showtime! |
|
I just need to make sure admin themes are tagged properly. 5 mins. |
|
OK, go for it! |
|
I think we're looking at a 4.8.9 before 4.9.0 hits the shelves. PHP minor releases are yearly, and if we're aiming for support then we should expect beta + release candidates from early summer onwards, release end of November 2022 - 10 months-ish away. So, do we spin Paging @bloatware, @Bloke & @philwareham for guidance. |
|
I'd rather move on from 4.8.x branch now - more work keeping two branches in sync. |
|
Fair point. It would be straightforward enough to spin a branch off |
|
Yeah, if we need 4.8.9, we can spin it off |
|
Awaiting confirmation from Paul at Pentest re: co-ordinated release of blog posts. ETA: 1600UTC. Assuming that goes to plan, I'll wrap up loose ends and we're done. |
|
Our sites are updated, release post goes live 1600UTC (two mins), I'll wrap up the rest of the stuff and we're done. |
|
Cheers Pete - great stuff. I cleared the cache at Cloudflare just to ensure the blog article appears for everyone (we have quite an aggressive cache there). |
|
Done. |
|
Super work everyone, and thanks Pete for taking the reins on the release. Another fabulous addition to the Textpattern release line. |
Uh oh!
There was an error while loading. Please reload this page.
We are targeting Textpattern 4.8.8 for release in Q4 2021 to provide initial support for PHP 8.1, address some snags, and provide further refinements. The release flight plan includes at least one beta release before the production release.
Please update this post and subsequent replies with tasks etc as needed, assigning yourself or others where appropriate.
Timeline
Repo Issues
Production Release
Personnel
Preflight
HISTORY.txt(everyone)HISTORY.txtwith additional information (release pilot or co-pilot)Take Off
latest.zipandlatest.tar.gzin server config (@petecooper)Inflight service
TXPversiononrpc.textpattern.com(release pilot, or assigned person)The text was updated successfully, but these errors were encountered: