Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: add dev blog post for distribution 2450 #2183

Merged
merged 1 commit into from
Dec 17, 2024

Conversation

jpraynaud
Copy link
Member

@jpraynaud jpraynaud commented Dec 17, 2024

Content

This PR includes a dev blog post announcing the release of the 2450 distribution.

Pre-submit checklist

  • Branch
    • Commit sequence broadly makes sense
    • Key commits have useful messages
  • PR
    • No clippy warnings in the CI
    • Self-reviewed the diff
    • Useful pull request description
    • Reviewer requested
  • Documentation
    • Add dev blog post (if relevant)

Issue(s)

Relates to #2124

@jpraynaud jpraynaud self-assigned this Dec 17, 2024
Copy link

Test Results

    4 files  ±0     52 suites  ±0   9m 53s ⏱️ +6s
1 428 tests ±0  1 428 ✅ ±0  0 💤 ±0  0 ❌ ±0 
1 639 runs  ±0  1 639 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit da80829. ± Comparison against base commit e66c3f6.

@jpraynaud jpraynaud temporarily deployed to testing-sanchonet December 17, 2024 11:07 — with GitHub Actions Inactive
@jpraynaud jpraynaud changed the title Docs: add dev blog post for distribution '2450' Docs: add dev blog post for distribution 2450 Dec 17, 2024
Copy link
Collaborator

@sfauvel sfauvel left a comment

Choose a reason for hiding this comment

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

LGTM

@jpraynaud jpraynaud merged commit 461e086 into main Dec 17, 2024
51 of 54 checks passed
@jpraynaud jpraynaud deleted the jpraynaud/2124-dev-blog-post-distribution-2450 branch December 17, 2024 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants