Page MenuHomePhabricator

Release MediaWiki 1.27.6/1.30.2/1.31.2/1.32.2
Closed, ResolvedPublic

Description

Previous release work: T199021

Tracking for activities actually pertaining to making the release of MediaWiki 1.27.6/1.30.2/1.31.2/1.32.1

Related Objects

StatusSubtypeAssignedTask
StalledNone
ResolvedNone
Resolvedakosiaris
ResolvedJdforrester-WMF
ResolvedJdforrester-WMF
ResolvedReedy
ResolvedReedy
ResolvedBawolff
ResolvedAnomie
ResolvedBawolff
ResolvedBawolff
ResolvedLegoktm
ResolvedLucas_Werkmeister_WMDE
ResolvedBawolff
Resolvedsbassett
Resolvedsbassett
ResolvedJdforrester-WMF
Resolvedsbassett
Resolvedsbassett
ResolvedReedy
ResolvedReedy
ResolvedJdforrester-WMF
ResolvedReedy
ResolvedReedy
ResolvedReedy
ResolvedJdforrester-WMF
ResolvedJdforrester-WMF
ResolvedReedy
ResolvedReedy
ResolvedReedy

Event Timeline

Reedy renamed this task from Release MediaWiki 1.27.6/1.30.2/1.31.2 to Release MediaWiki 1.27.6/1.30.2/1.31.2/1.32.1.Feb 13 2019, 2:23 AM
Reedy updated the task description. (Show Details)

! In T213595#4972704, @greg wrote:

! In T213595#4949955, @Legoktm wrote:
Can we bundle the planned security release with this?

Did that ^ happen?

I'm not aware of any security patches that landed in 1.32.1 but I haven't announced the release yet if we want to rebuild the tarballs it's fine with me.

What does anyone want to do? It's going to take probably a week or two to get things finished off with other stuff going on...

Do we want to wait with 1.32.1? Or get that out of the door, and do a 1.32.2 a few weeks later?

I know that doesn't look particularly great; though it would be worse as two security releases in a short period

Well, I already built the 1.32.1 tarballs but I haven't announced the release officially nor have I pushed the tags to git. I don't have a strong opinion either way.

Let's do separate releases. We want to do these more frequently anyway, right?

Reedy renamed this task from Release MediaWiki 1.27.6/1.30.2/1.31.2/1.32.1 to Release MediaWiki 1.27.6/1.30.2/1.31.2/1.32.2.Apr 30 2019, 6:28 PM
Reedy changed the visibility from "Custom Policy" to "Public (No Login Required)".Jun 6 2019, 3:58 PM