From ecd99de3c5078db408b8ada2fab990bc4dafe3fe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Pfeuffer?= Date: Mon, 19 Aug 2024 13:11:47 +0200 Subject: [PATCH] Clean up release process documentation --- docs/en/release-process.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/docs/en/release-process.md b/docs/en/release-process.md index 3cc32c0ca6..6f9366fb31 100644 --- a/docs/en/release-process.md +++ b/docs/en/release-process.md @@ -1,4 +1,4 @@ -# How to release SCM-Manager v2 core (Script) +# How to release SCM-Manager core (Script) The most easy way to release the core is to use the release script. This will guide you through all necessary tasks. @@ -23,7 +23,7 @@ It will # Manual core release -To release a new version of SCM-Manager v2 "manually", you have to do the following steps +To release a new version of SCM-Manager "manually", you have to do the following steps (replace placeholders `` accordingly, eg. with `2.1.0`): ## Check out default branch @@ -144,13 +144,9 @@ How these conflicts should be merged depends on the version that has been releas - If the hotfix is the new main, you should take this new version and then manually create a new SNAPSHOT based on the new hotfix version number using gradle: `./gradlew setVersionToNextSnapshot`. -# How to release SCM-Manager v2 plugins +# How to release SCM-Manager plugins -To release a new version of a Plugin for SCM-Manager v2 you have to do the following steps (replace placeholder `` accordingly, eg. with `2.1.0`): - -## Attention: Migrate plugin to gradle -If an SCM-Manager plugin hasn't been migrated to gradle yet, this is highly recommended before release the next version. -The migration from maven to gradle can easily be done using [this tool](https://github.com/scm-manager/smp-maven-to-gradle). +To release a new version of a Plugin for SCM-Manager you have to do the following steps (replace placeholder `` accordingly, eg. with `2.1.0`): ## Check out default branch