Since just prior to 1.19 branching, a group of developers managing the various Foreman and Katello releases have been meeting regularly to check on status, identify blockers, action items and how we plan to resolve them. After 1.19 was released, we decided to do a retrospective of the process. The following are the generalized notes from that and will serve as dicussion points within this thread for how we improve on each point.
- Good Recap
- Increased communication via release meetings
- Increased communication and transparency via discourse posts
- 1.19 schedule being on track
- RC test week helped identify regressions prior to GA
- Katello releases quickly follow core releases
- Improved nightly stability
- Improvements
- More automation
- Release job updates
- Release_mash to tarballs-release
- Release job updates
- Defined process improvements
- Can we simplify the release process?
- Define the cherry-picking process for each project
- Strategy to handle hand-off of issues to different time-zones, status reporting
- Increased discourse communication
- Release meeting structured
- Increase community participation in release meetings
- Adding meeting to event calendar
- Meeting notes
- Cadence of meetings
- Fluid based on number of releases?
- Increase community participation in release meetings
- CI code change testing
- Parallelizing RPM and Deb pipelines for releases?
- Katello release docs need overhaul
- Add package owner and release owner definitions
- Improved testing
- Defining hammer release process
- More automation