Skip to content

Release Retro 24.11.1 #684

@NickLarsenNZ

Description

@NickLarsenNZ

Part of #683.

After the 24.11.1 release, we will hold a release-retro to discuss what went well, and find out where we can improve.

  • Schedule the retro
  • Create action items during the retro

The task list below can capture items as we think of them.

### Items for discussion
- [ ] The new `--release` flag is really nice. Made demo testing much faster. Thanks @labrenbe
- [ ] The demo updates script needs some work (See: https://github.com/stackabletech/demos/pull/138). Maybe it shouldn't infer anything, and ask or take args.
- [ ] Release branches of the documentation must **not** mention HEAD or main in the list of branches in the Antora playbooks as it will break CI **and** local builds, see https://github.com/stackabletech/documentation/pull/705
- [ ] The documentation repository uses release branches named `release/YY.M` . Instead `release-YY.M` should be used to have unified branch names across all repos. Or the other way around, I personally don't care, but it is more effort.
- [ ] Workflow for required demo changes for a release. See Slack thread in [#team-demos](https://stackable-workspace.slack.com/archives/C04072NLUP7/p1738246913557429).

Tip

During the retro, edit this description and remove the commented actions task list below

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions