[BIGTOP-1463] We need a better automation of the release process.

• Type: Bug
• Status: Open
• Priority: Blocker
• Resolution: Unresolved
• Affects Version/s: 0.8.0
• Fix Version/s: backlog
• Component/s: build
• Assignee: Unassigned
• Reporter: Konstantin I Boudnik
• Created: 28/Sep/14 02:18
• Updated: 08/Apr/17 00:14

Description

At the moment, the release process is driven by the wiki page https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
The info is very helpful, but it needs to be updated and also requires a number of manual steps.

Let's have a one-command release process that will include all needed steps like iTest, test artifacts uploads. as well as site creation and release artifacts deployment.

Issue Links

• is related to: BIGTOP-2736 Automate last mile of release process

Sub-Tasks

• released source code is not same with source code in branch: Resolved
• automate to include known issues in release notes: Open
• Fix RAT plugin configuration to be able to RAT-validate all published artifacts: Resolved
• Avoid running top-level assembly while doing deploy for subprojects: Resolved
• Getting rid of md5 and sha1 for release artifacts: Open
• Update maven rat config to match one from gradle: Resolved
• release assembly needs to include bigtop_toolchain: Resolved
• Wrap separate maven release steps into convenient gradle task: Resolved