[KIEKER-328] Additional automation in release creation process

kieker-monitoring / kieker

Kieker's main repository

Apache License 2.0

70 stars 41 forks source link

[KIEKER-328] Additional automation in release creation process #902

Open rju opened 1 week ago

rju commented 1 week ago

JIRA Issue: KIEKER-328 Additional automation in release creation process Original Reporter: Andre van Hoorn

E.g.,

Step 6 (Download all release files) of wiki:DevGuide#CreatingaRelease, i.e., download release files and compare md5sums
Steps 7,8 (Upload release files and Javadoc to SF) of wiki:DevGuide#CreatingaRelease, including (if possible checksum check)

Checklist:

rju commented 3 days ago

author nils-christian -- Fri, 4 Apr 2014 13:15:51 +0200

Not for 1.9 I assume?

rju commented 3 days ago

author André van Hoorn -- Fri, 4 Apr 2014 14:26:14 +0200

Replying to [nie|comment:1]:
> Not for 1.9 I assume?

Maybe, because I usually do these improvements as part of the release process

rju commented 3 days ago

author André van Hoorn -- Wed, 16 Apr 2014 10:26:25 +0200

Don't see much more potential to automate. In my opinion, the required steps are nicely described in wiki:DevGuide#CreatingaRelease and get updated during each release creation. Some time could be saved by automating comparisons of checksums, which are required in at least three steps but this is really minor.