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

Add 2.19 roadmap #2138

Merged
merged 7 commits into from
Dec 4, 2024
Merged

Add 2.19 roadmap #2138

merged 7 commits into from
Dec 4, 2024

Conversation

sivel
Copy link
Member

@sivel sivel commented Nov 12, 2024

No description provided.

@ansible-documentation-bot
Copy link
Contributor

Thanks for your contribution, @sivel! Please make sure that your pull request includes sufficient and meaningful details in the description.
PR descriptions provide important context and allow other developers and our future selves to understand a change's rationale and what it actually fixes or accomplishes.

@mariolenz
Copy link
Contributor

Any news on this?

It would be great to have something official about when core is planning to release alphas / betas / rcs and 2.19. Even if it isn't clear yet what's on the roadmap to implement for this version...

@oraNod
Copy link
Contributor

oraNod commented Dec 2, 2024

@sivel Rather than adding to the ignored words list, you could add the entire line to https://github.com/ansible/ansible-documentation/blob/devel/.codespellignorelines

This way it will ignore the one instance in your changes but still catch misspellings of "studio".

@sivel sivel marked this pull request as ready for review December 2, 2024 16:23
@sivel
Copy link
Member Author

sivel commented Dec 3, 2024

This is ready for review/merge now. Let me know if you need anything further.

Copy link
Contributor

@oraNod oraNod left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks @sivel

I'd like to get at least one approval from a SC member before we merge.

@oraNod oraNod requested a review from a team December 4, 2024 11:27
@oraNod oraNod added the no_backport This PR should not be backported. devel only. label Dec 4, 2024
@mariolenz
Copy link
Contributor

I'd like to get at least one approval from a SC member before we merge.

I won't approve because I'm interested in seeing this merged. That is, I feel too biased to review.

But since @Andersson007 and @gundalow approved...

@oraNod oraNod merged commit 6bda95b into ansible:devel Dec 4, 2024
11 checks passed
@oraNod
Copy link
Contributor

oraNod commented Dec 4, 2024

Thanks @sivel 🚀

@mariolenz mariolenz mentioned this pull request Dec 4, 2024
@samccann
Copy link
Contributor

samccann commented Dec 4, 2024

Coming in late but @oraNod - why is a core roadmap subject to SC approval?

@oraNod
Copy link
Contributor

oraNod commented Dec 4, 2024

Coming in late but @oraNod - why is a core roadmap subject to SC approval?

it isn't to be fair. I guess I was aware that SC folks were looking at this PR and I didn't want to merge too soon if they had questions etc. probably should have phrased things differently.

@felixfontein
Copy link
Collaborator

Maybe next time do something like CC @ansible/steering-committee instead of requesting a review, then it's clear to everyone that it's not asking for approval, but simply pinging for information (and potential comments/questions) :)

@oraNod
Copy link
Contributor

oraNod commented Dec 5, 2024

Maybe next time do something like CC @ansible/steering-committee instead of requesting a review, then it's clear to everyone that it's not asking for approval, but simply pinging for information (and potential comments/questions) :)

will do. apologies if I caused some misunderstanding (or if my misunderstanding caused some annoyance). I guess I've been on a bit of a streak this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no_backport This PR should not be backported. devel only.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants