[KIEKER-1800] Restructure Release Process

[rju]

JIRA Issue: KIEKER-1800 Restructure Release Process Original Reporter: Reiner Jung

---

I had a look at https://kieker-monitoring.atlassian.net/wiki/spaces/DEV/pages/5865680/Release+Creation
and identified X potential changes we can perform easily and already for the 1.14 release:

• 4.1 Sourceforge is already marked deprecated. People use mvn repositories to download archives or they let their build system do it. I almost never use Sourceforge (only for deprecated software).
• A wide range of tool script tests are no longer necessary in Kieker 1.15-SNAPSHOT, as the tools can be tested completely with unit tests. Also some tools are deprecated in 1.15. and new tools have been built with gradle in separate release files.
• Example testing should not be performed through gradle. This should be (a) extracted and (b) examples should be separated anyway, as Kieker is moving from teaching tool to scientific framework/used framework.

In addition I flagged all "manual" tasks in the release document.

[rju]

author rju -- Thu, 26 Sep 2019 10:05:36 +0200

Also involves KIEKER-1433 Done

[rju]

author rju -- Sun, 12 Jul 2020 16:57:55 +0200

The source release is identical to the Kieker stable branch and a suitable tarball is provided by github https://github.com/kieker-monitoring/kieker/archive/stable.zip

This reduces build time by 50%

[rju]

author rju -- Thu, 26 Sep 2019 10:05:36 +0200

Also involves KIEKER-1433 Done

[rju]

author rju -- Sun, 12 Jul 2020 16:57:55 +0200

The source release is identical to the Kieker stable branch and a suitable tarball is provided by github https://github.com/kieker-monitoring/kieker/archive/stable.zip

This reduces build time by 50%

[rju]

author rju -- Tue, 3 Nov 2020 14:57:33 +0100

Build time reduction works.

[rju]

author rju -- Wed, 24 May 2023 14:22:47 +0200

I this we can drop this ticket. We have done most of it and other tickets may cover the remaining issues.