There is no 0.4.0 release?
#779
Closed
opened 4 years ago by matthiasbeyer
·
8 comments
No Branch/Tag Specified
paginate-search-init
main
s3
fix-delete-user
timeline-cli
blog-title
signature
remove-dup-images
ldap-non-anon
drone-ci
DearRude/force-lang
igalic/go/async-all-mut
go/async
floreal/translations-update
missing-docs
RAOF/fix-arm64-build
epsilon-phase/authorized-fetch
upgrade
improve-the-editor-once-again
igalic/feat/custom-fairing-domains
feature/ldap
test/dotenv_error
fix-mobile-margin
0.7.2
0.7.0
0.2.0-alpha-1
0.3.0-alpha-2
0.4.0-alpha-4
0.5.0
0.6.0
0.7.1
Labels
Clear labels
Related to the REST API
Code running on the server
Stuff related to Federation
Related to the front-end
Translations, and related code
More about project management or code than the project itself
The building, or installation process of Plume
Something isn't working
We need to talk
New feature or request
This is a new feature
Compatibility with different browsers, readers and OS
Related to an external package that Plume uses
UI/UX related issues and PRs
Good for newcomers
Extra attention is needed
Issues affecting only mobile UX
How elements're rendered out for the end user
Something else needs to be fixed first
This issue or pull request already exists
This PR is not complete yet
Issues concern a limited number of instances
This doesn't seem right
Need to be discussed by the community (on Loomio)
This PR is ready to be reviewed
Proposed ideas worth considering
This is issue has been created after a vote on Loomio
This will not be worked on
Apply labels
A: API
Related to the REST API
A: Backend
Code running on the server
A: Federation
Stuff related to Federation
A: Front-End
Related to the front-end
A: I18N
Translations, and related code
A: Meta
More about project management or code than the project itself
A: Security
Build
The building, or installation process of Plume
C: Bug
Something isn't working
C: Discussion
We need to talk
C: Enhancement
New feature or request
C: Feature
This is a new feature
Compatibility
Compatibility with different browsers, readers and OS
Dependency
Related to an external package that Plume uses
Design
UI/UX related issues and PRs
Documentation
Good first issue
Good for newcomers
Help welcome
Extra attention is needed
Mobile
Issues affecting only mobile UX
Rendering
How elements're rendered out for the end user
S: Blocked
Something else needs to be fixed first
S: Duplicate
This issue or pull request already exists
S: Incomplete
This PR is not complete yet
S: Instance specific
Issues concern a limited number of instances
S: Invalid
This doesn't seem right
S: Needs Voting/Discussion
Need to be discussed by the community (on Loomio)
S: Ready for review
This PR is ready to be reviewed
Suggestion
Proposed ideas worth considering
S: Voted on Loomio
This is issue has been created after a vote on Loomio
S: Wontfix
This will not be worked on
No Label
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#779
Reference in New Issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
In your blog you write that plume 0.4.0 is out but there is no tag in the repository.
Please provide one.
Tag is actually
0.4.0-alpha-4
So the blog article is wrong because there is no 0.4.0 release yet?
"alpha-4" is an "alias" for 0.4, sorry if it is confusing. 😅
How come? "0.4.0-alpha-4" is clearly not "0.4.0", it is still an alpha release before the actual 0.4.0 release is out.
At least that's what a user would expect. After the 0.4.0-alpha-4, I would either expect
release!
Whut? Now that I had a closer look on the release page, it is even more confusing!
Basically, you released no version yet. You went from
"0.2.0-alpha-1" (which really should be "0.1.0-alpha.1") to
"0.3.0-alpha-2" (which really should be "0.1.0-alpha.2") to
"0.4.0-alpha-4" (which really should be "0.1.0-alpha.3").
So you did not only jump to "0.4" without ever releasing "0.1.0", "0.2.0" or "0.3.0", you even did jump to "0.4.0-alpha-4" without ever releasing "0.4.0-alpha-{1,2,3}"...
So basically it is double-counter-intuitive.
Although semver explicitely states that 0.y.z releases should not be considered stable and everything might happen, packeteers and users are confused and if they only see that there's a "0.4.0-alpha-anything" that there already is a 0.3.0 release they might test. Ugh.
Well, I'm not sure where to go from here. What is the right thing to do now? Deleting tags is strongly discouraged, so it is not an option and might break experiemental deployments all over the place (essentially breaking users deployments by vanishing... not a good thing)!
So all you could do is make the next release 0.4.0 and then start following semver properly from there. Everything else is just too confusing for users, packaging people (which is my role in this) and everyone else.
So that's my suggestion: Release 0.4.0 as soon as you're comfortable with the code being ready, then follow semver and make the next releases 0.5.0, 0.6.0 and so on!
Hope you're not discouraged by this issue from releasing your code! I really hope that I can use plume myself one day and I'm really looking forward to that day! Happy hacking! 😃
I must admit that this versioning is not 100% semver-compliant… 😅 Maybe we should indeed just use
0.5.0
,0.6.0
, etc, for future releases. I don't know what other contributors think?We just published Plume 0.5.0, without any suffix in the tag name. We will follow this scheme from now. I hope this fixes your issue. Please re-open if it doesn't.
🎉 awesome!