updates #2892
Merged
updates #2892
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
@nf-core-bot fix linting |
Contributor
Author
|
@nf-core-bot fix linting |
mashehu
reviewed
Dec 9, 2024
sites/main-site/src/content/blog/2024/maintainers-minutes-2024-11-29.mdx
Outdated
Show resolved
Hide resolved
jfy133
reviewed
Dec 9, 2024
sites/main-site/src/content/blog/2024/maintainers-minutes-2024-11-29.mdx
Outdated
Show resolved
Hide resolved
| Jon brought up that different pipelines take different approaches, and few follow 'true' SemVer rules. | ||
| The main issue was 'major releases': in SemVer, going from 1.0.0 to 2.0.0 indicates a _breaking change_, where the way a user (or computer) interacts with the software has changed in a way that the way they are used to using the software will not work any more. | ||
| However in many nf-core pipelines, developers have used the major version bump to indicate major new functionalities or large back-end refactoring of the code base, even if it doesn't affect the way a user interacts with the pipeline. | ||
| Jon pointed out that different pipelines take different approaches, with few adhering strictly to ‘true’ SemVer rules. The primary issue revolved around ‘major releases.’ According to SemVer, transitioning from version 1.0.0 to 2.0.0 signifies a breaking change—a change that alters the software’s functionality such that existing usage patterns no longer work. However, many nf-core pipelines have used major version bumps to indicate substantial new functionalities or extensive back-end codebase refactoring, even when these changes do not disrupt user interactions. |
Member
There was a problem hiding this comment.
One sentence per line please! (throughout)
sites/main-site/src/content/blog/2024/maintainers-minutes-2024-11-29.mdx
Outdated
Show resolved
Hide resolved
sites/main-site/src/content/blog/2024/maintainers-minutes-2024-11-29.mdx
Outdated
Show resolved
Hide resolved
Contributor
Author
|
@nf-core-bot fix linting |
1 similar comment
Contributor
|
@nf-core-bot fix linting |
jfy133
approved these changes
Dec 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@netlify /blog/2024/maintainers-minutes-2024-11-29