Create a landing wiki page for MediaWiki release management
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Qgil
	Aug 19 2014, 12:20 PM

Description

We need a landing page for MediaWiki release management including a basic explanation of the activity, status reports, and links to wherever appropriate. We are almost there:

https://www.mediawiki.org/wiki/Project:Release_management could be the starting point. Wouldn't it be better in the Main namespace, like the rest of the development projects? @gpaumier, can you enable status reports in that page as soon as we agree on its name?
https://www.mediawiki.org/wiki/Release_Manager_(MediaWiki) exists too. I would merge it with the previous one.

Details

Reference: fl547

Reference	Source Branch	Dest Branch	Author	Title
repos/cloud/toolforge/toolforge-deploy!260	bump_builds-api	main	project_1317_bot_df3177307bed93c3f34e421e26c86e38	builds-api: bump to 0.0.143-20240415191619-ae83a3bc
repos/cloud/toolforge/envvars-api!28	update_oapi_codegen	main	raymond-ndibe	[envvars-api] update oapi-codegen
repos/cloud/toolforge/toolforge-deploy!258	bump_builds-api	main	project_1317_bot_df3177307bed93c3f34e421e26c86e38	builds-api: bump to 0.0.140-20240415133504-9d56e2c4
repos/cloud/toolforge/toolforge-deploy!257	bump_envvars-api	main	project_1317_bot_df3177307bed93c3f34e421e26c86e38	envvars-api: bump to 0.0.43-20240415133149-ec8b039e
repos/cloud/toolforge/envvars-api!27	allow_configuring_address	main	dcaro	main: allow configuring the address
repos/cloud/toolforge/builds-api!88	configure_address	main	dcaro	main: allow configuring address
repos/phabricator/extensions!32	T362047gitlabPatchesColumns	wmf/stable	aklapper	GitLab Patches: Improve order of columns
repos/phabricator/extensions!31	T362047gitlabPatchesColumns	wmf/stable	aklapper	GitLab Patches: Improve order of columns
repos/releng/scap!274	work/swfrench/T362437-run-testserver-checks	master	swfrench	Run testserver checks in --k8s-only mode
repos/releng/scap!273	work/swfrench/T362437-pause-after-sync	master	swfrench	Support --pause-after-testserver-sync in --k8s-only mode
repos/cloud/toolforge/api-gateway!17	slavina/add-oapi-server	main	sstefanova	[oapi-spec] add oapi-server to gateway
repos/commtech/wishlist-intake!4	T362274	main	musikanimal	Rename CategorySection to TaskSection
repos/security/wikimedia-code-health-check!39	T362348-minor-batch-runner-changes	main	sbassett	Minor batch runner changes
repos/cloud/toolforge/builds-api!86	update_oapi_codegen	main	raymond-ndibe	[builds-api] update oapi-codegen
repos/commtech/wishlist-intake!3	category-section	main	musikanimal	Implement 'Category' section and rework entrypoint
repos/abstract-wiki/wikifunctions/function-orchestrator!157	T362271	main	jforrester	db: Call wikilambda_fetch with uselang=content to aide caching
repos/cloud/toolforge/jobs-cli!27	bump_to_16.0.7	main	dcaro	d/changelog: bump to 16.0.7
repos/cloud/toolforge/jobs-cli!26	fix_filelog_on_dump	main	dcaro	cli: use the boolean value for filelog
repos/cloud/toolforge/alerts!11	add_d_processes_alert	main	dcaro	kubernetes: add workers with D stuck processes alert
repos/movement-insights/movement-metrics!9	prune_charts_and_data	main	nshahquinn-wmf	Remove unnecessary metrics and charts and make all Wikicharts code work

Event Timeline

Mglaser wrote on 2014-08-19 12:23:32 (UTC)

I'm on it just now. We will use https://www.mediawiki.org/wiki/Project:WikiReleaseTeam as a landing page. This is where the reporting and logging goes. Topics of overall interest, like "Backporting policy", "Release timeline" and "Release checklist" will go in the main space.

Mglaser wrote on 2014-08-19 12:24:18 (UTC)

As I have not yet implemented the changes, I'm of course open to suggestions :)

qgil wrote on 2014-08-19 13:07:04 (UTC)

◀ Merged tasks: T545.

qgil wrote on 2014-08-19 13:08:24 (UTC)

I don't have a strong opinion as long as we have one single page that is easy to find.

Mglaser wrote on 2014-09-04 22:36:23 (UTC)

Ok, most of the restructuring is done. I am not sure about the release timeline: https://www.mediawiki.org/wiki/Project:WikiReleaseTeam/Release_timeline . This seems to be operational and not descriptive. So for now I left it in the projeect space.

Another open question: should we have a pointer from the main space to Project:WikiReleaseTeam, as articles in the project space don't show up in the search unless explicitly requested?

Mglaser wrote on 2014-09-04 22:45:25 (UTC)

For now, I just added a "See also" to https://www.mediawiki.org/wiki/Branch_points. This is where https://www.mediawiki.org/wiki/Releases redirects to.

greg wrote on 2014-09-04 22:46:28 (UTC)

I still think everything should be in the main namespace to allow discoverablity, especially things like the release timeline that people will have an interest in.

In T547#7, @Qgil wrote:

I don't have a strong opinion as long as we have one single page that is easy to find.

Searching for "release timeline" from the main page of mediawiki.org give me: https://www.mediawiki.org/w/index.php?search=release+timeline&title=Special%3ASearch&go=Go which is what any user would do. By Quim's requirement ("easy to find") everything should be in the main namespace. IMHO. No reason to hide it.

Mglaser wrote on 2014-09-04 22:49:05 (UTC)

Ok, moved everything to main. There is a page "WikiReleaseTeam" now.

importing issue status

• flimport closed this task as Resolved.Sep 12 2014, 1:45 AM

Palexis moved this task from Backlog to Resolved on the Wiki-Release-Team board.Sep 25 2014, 11:39 PM

• flimport assigned this task to Mglaser.Oct 2 2014, 9:55 PM

• flimport added a subscriber: MarkAHershberger.

• flimport added a subscriber: Mglaser.

• flimport added a subscriber: greg.Oct 2 2014, 9:58 PM

• flimport added a subscriber: gpaumier.Oct 8 2014, 12:00 PM