parsoid REL1_36 branch and tag
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Reedy
	Apr 15 2021, 4:45 PM

Description

Not sure exactly how we want to handle it... but at some point I guess there should be a REL1_36 parsoid branch, a tag for use in the eventual 1.36.0 release (v0.13.0 or similar?)... And then for 1.37/master, the tags bumping to v14

Details

Subject	Repo	Branch	Lines +/-
composer: Lock Parsoid version to specific 0.13.0 release	mediawiki/core	REL1_36	+1 -1
Bump wikimedia/parsoid to "release version" 0.13.0	mediawiki/vendor	REL1_36	+436 -264
Bump wikimedia/parsoid to "release version" 0.13.0	mediawiki/vendor	REL1_36	+436 -264

Customize query in gerrit

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Resolved		None	T279455 Release MW 1.36.0
		Resolved		cscott	T280270 parsoid REL1_36 branch and tag

Event Timeline

Reedy created this task.Apr 15 2021, 4:45 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 15 2021, 4:45 PM

Reedy added a parent task: T279462: Release 1.36.0-rc.0.Apr 15 2021, 4:46 PM

Jdforrester-WMF subscribed.Apr 15 2021, 4:47 PM

DannyS712 updated the task description. (Show Details)Apr 15 2021, 5:44 PM

Reedy moved this task from Blocker to Process on the MW-1.36-release board.Apr 15 2021, 6:10 PM

Arlolra added a subtask: T261329: Prepare Parsoid for MW.Apr 15 2021, 6:46 PM

Arlolra edited projects, added Parsoid (Third-party); removed Parsoid.

• ssastry removed a subtask: T261329: Prepare Parsoid for MW.Apr 26 2021, 3:33 PM

I Was Bold and branched REL1_36 at da46f35324478afe319b311044a9d17738a7cb29, slightly after the last 0.13.0 release (0.13.0-a32). I needed a specific commit to refer to for T261220.

We'll probably want to release a 0.13.0-a33 release to match where REL1_36 is currently sitting, but I want to finish T261220 and make sure there's nothing else which should be included in -a33 first.

Jdforrester-WMF mentioned this in T261220: Zero Config Install of VE + Parsoid for MW 1.36.Apr 27 2021, 3:07 PM

Jdforrester-WMF edited parent tasks, added: T279455: Release MW 1.36.0; removed: T279462: Release 1.36.0-rc.0.Apr 28 2021, 3:57 PM

In T280270#7035986, @cscott wrote:

I Was Bold and branched REL1_36 at da46f35324478afe319b311044a9d17738a7cb29, slightly after the last 0.13.0 release (0.13.0-a32). I needed a specific commit to refer to for T261220.

We'll probably want to release a 0.13.0-a33 release to match where REL1_36 is currently sitting, but I want to finish T261220 and make sure there's nothing else which should be included in -a33 first.

Anything I can do to help with these last fiddles?

I was just waiting to see if there was a hue and cry or wailing and gnashing of teeth in rc.0 (ie, did T261220 work or did I break something) -- assuming that folks are happy with that and we don't need any further Parsoid patches then I think we can just go ahead and tag the 0.13.0.

In T280270#7075336, @cscott wrote:

I was just waiting to see if there was a hue and cry or wailing and gnashing of teeth in rc.0 (ie, did T261220 work or did I break something) -- assuming that folks are happy with that and we don't need any further Parsoid patches then I think we can just go ahead and tag the 0.13.0.

Let's do that.

Universal_Omega subscribed.May 24 2021, 6:37 PM

Parsoid v0.13.0 has been tagged, since I have not heard wailing and gnashing of teeth.

Change 693970 had a related patch set uploaded (by Jforrester; author: Jforrester):

[mediawiki/core@REL1_36] composer: Lock Parsoid version to specific 0.13.0 release

https://gerrit.wikimedia.org/r/693970

gerritbot added a project: Patch-For-Review.May 24 2021, 10:34 PM

Change 693971 had a related patch set uploaded (by Jforrester; author: Jforrester):

[mediawiki/vendor@REL1_36] Lock Parsoid version to specific 0.13.0 release

https://gerrit.wikimedia.org/r/693971

Change 693972 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):

[mediawiki/vendor@REL1_36] Bump wikimedia/parsoid to "release version" 0.13.0