Consider a devel branch, making main stable
Closed, ResolvedPublicSpike
Actions

Assigned To

None

Authored By

	• roti_WMDE
	Sep 6 2024, 10:19 AM

Description

Current Situation:

At the moment our latest developments happen in main
main is also what users intuitively check out
We do not have a branch that always contains latest stable, but this changes from deploy-3 to deploy-4... making it impossible to reference "latest stable" in documentation that does not need constant adjustments. Related: T371456: Question about part of deploy README text

Goal:

Make it easy to get the latest stable version for users
Have the latest stable version in a fixed location to refer to it
Have a place where development happens without constantly changing code users checkout

Acceptance Criteria:

[optional] Notes:

[optional] Open Questions:

		Status	Subtype	Assigned	Task
		Resolved	Spike	lojo_wmde	T377181 Release engineering and process follow-up to single-track release decision
		Resolved	Spike	None	T374211 Consider a devel branch, making main stable

Restricted Application changed the subtype of this task from "Task" to "Spike". · View Herald TranscriptSep 6 2024, 10:19 AM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

In our retreat, we considered it the other way around:

keep main as unstable in order to have easy dev workflows
offer a place to users to find stable version downloads and documentation outside of our dev repo

• roti_WMDE claimed this task.

• roti_WMDE removed • roti_WMDE as the assignee of this task.