Page MenuHomePhabricator

Use semantic versioning for services (for consistency with mediawiki core)
Closed, ResolvedPublic

Description

I'd like to unify the way we do release branches / tags and semantic versioning is a perfectly good way to do that. Since we already want to use semantic versioning in a few other places, I think we should use it for deployment tags (this depends on the new tooling currently in development and would replace the numeric tag identifiers used by trebuchet)

Related Objects

StatusSubtypeAssignedTask
DeclinedNone
OpenNone
Resolveddemon
Declinedmmodell
ResolvedLegoktm
Resolved GWicke
Resolvedmmodell
Resolved GWicke
Declined GWicke
Resolvedthcipriani
DeclinedNone
Resolvedmobrovac
Resolvedakosiaris
Resolvedakosiaris
Declinedmmodell
InvalidNone
Resolvedmmodell
ResolvedJdforrester-WMF
Declinedmmodell
Resolvedmmodell
Resolvedmmodell
Resolvedmmodell
Resolveddduvall
ResolvedKrinkle
ResolvedKrinkle
Resolvedmmodell
DuplicateKrinkle
ResolvedKrinkle
ResolvedKrinkle
ResolvedPRODUCTION ERRORMaxSem
ResolvedKrinkle
ResolvedKrinkle
ResolvedKrinkle
ResolvedKrinkle
ResolvedKrinkle
Resolvedmmodell
ResolvedNone
ResolvedJoe
ResolvedNone
ResolvedJoe

Event Timeline

mmodell raised the priority of this task from to Low.
mmodell updated the task description. (Show Details)
mmodell added projects: Services, Deployments.
mmodell added subscribers: Legoktm, greg, Mglaser and 6 others.

How does MediaWiki core fit into this? It does not use semver compliant versioning...

We generally use semver for node services and libraries. Release versions are tagged with vX.Y.Z.

GWicke claimed this task.

Yup, was mostly waiting for your feedback as the owner. Resolving.