Skip to content

feat: add release schedule page#251

Open
robobario wants to merge 1 commit intokroxylicious:mainfrom
robobario:release-schedule
Open

feat: add release schedule page#251
robobario wants to merge 1 commit intokroxylicious:mainfrom
robobario:release-schedule

Conversation

@robobario
Copy link
Copy Markdown
Member

Adds a release schedule page to provide visibility into planned and released versions of Kroxylicious. This helps users and contributors track upcoming releases and their target dates.

The page includes milestones linked to GitHub for detailed tracking.

Adds a Footer link

Assisted-by: Claude Sonnet 4.5 noreply@anthropic.com

image

Adds a release schedule page to provide visibility into planned and
released versions of Kroxylicious. This helps users and contributors
track upcoming releases and their target dates.

The page includes milestones linked to GitHub for detailed tracking.

Assisted-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Signed-off-by: Robert Young <robertyoungnz@gmail.com>
@robobario robobario requested a review from a team as a code owner April 29, 2026 08:50
Copy link
Copy Markdown
Member

@SamBarker SamBarker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

would be great to tie this into project/milestone due dates in GitHub but lets start with something simple.

@robobario
Copy link
Copy Markdown
Member Author

yeap, could also imagine having some kind of integration with the release metadata, so we could populate an entry in the table for each metadata file in _data/release with status 'released' and link to something relevant.

Hmm, I wonder if the planned releases could have a metadata file each that are ignored by the other bits of the website. Then at release time it's overwritten.

@robobario
Copy link
Copy Markdown
Member Author

will wait til we've got some agreement on the dates on the dev-list

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants