docs(archi): add package publish chapter (394096b2) · Commits · to be continuous... / to be continuous documentation

docs/dev/architecture.md

+7 −2

Original line number	Diff line number	Diff line
		@@ -18,8 +18,6 @@ Here is the list of common _to be continuous_ features that must be implemented
		* [Merge Request Workflow](../usage.md#merge-request-workflow) by default, globally overridable
		* [Adaptive Pipeline strategy](../usage.md#test-analysis-jobs-rules) by default, globally overridable

		<!-- * release management & package publishing, -->

		## Standard stages

		Every template shall reuse defined [generic pipeline stages](../understand.md#generic-pipeline-stages).
		@@ -166,3 +164,10 @@ We decided to observe the same delay before implementing a non-backward compatib
		I.e. wait that the GitLab version that introduced the feature is the oldest version maintained by GitLab.

		In practice, this is about 3 months.

		## Package publish

		Each template capable of publishing (versioned) packages, shall implement it according to the [common publish design](../understand.md#publish).

		Decorelating the publish job from the release process ensures that all publish-capable templates will always take care of publishing their own package(s),
		whichever the technique that was used to trigger the release (manual, semantic-release or any other alternative).