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

Improve contributor documentation #4038

Merged
merged 4 commits into from
Mar 13, 2024
Merged

Conversation

durban
Copy link
Contributor

@durban durban commented Mar 9, 2024

Hopefully fixes #4005. I don't actually know, how releasing works, this is me trying to understand it.

@durban durban linked an issue Mar 9, 2024 that may be closed by this pull request
@durban durban marked this pull request as ready for review March 9, 2024 21:37
RELEASING.md Outdated Show resolved Hide resolved
RELEASING.md Outdated Show resolved Hide resolved
RELEASING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated
When in doubt, just target your work against `series/3.x`. If you're *very* certain that your changes will be source- *and* forward-compatible, it's safe to target the latest major/minor series (e.g. `series/3.4.x`). Note that forward-compatibility means that you cannot *add or remove* an API, while backward-compatibility means you cannot *remove* an API.

With documentation changes (both Scaladoc and Markdown documentation in `/docs`), target the *earliest* branch to which those changes are relevant. For example, if a method already exists in `series/3.4.x`, documentation about it should also go into `series/3.4.x`. On the other hand, if that method was only added in `series/3.x`, its documentation should go into `series/3.x`.
Copy link
Member

Choose a reason for hiding this comment

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

Maybe we need to clarify "earliest maintained branch" or something e.g. do not send changes to series/3.4.x because our current active minor branch is series/3.5.x.

Honestly, we should update this contributing doc every time we release a minor. That will help stave off confusion :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, that makes sense. I did it for the current version.

RELEASING.md Show resolved Hide resolved
@djspiewak djspiewak merged commit 1cce460 into typelevel:series/3.5.x Mar 13, 2024
28 of 31 checks passed
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.

Improve contributor documentation
3 participants