bootandy/archived-dust
1
0
Fork 0
mirror of https://github.com/bootandy/dust.git synced 2026-06-08 11:29:05 +03:00
Code Issues 21 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #68] Suggestion: stick to semantic versioning #29

New Issue
Closed
opened 2026-06-08 11:25:22 +03:00 by zhus · 2 comments
zhus commented 2026-06-08 11:25:22 +03:00
Owner
Copy Link
Copy Source

Originally created by @jc21 on GitHub (Feb 10, 2020).
Original GitHub issue: https://github.com/bootandy/dust/issues/68

Looking through your release history, your versioning scheme is all over the place.

I'm packaging your software on my Centos and Debian repositories and it's easier for me if the version is of a consistent standard, v0.0.0. In these package managers, v4 is newer than your latest release of v0.4.5.0. I would argue that you don't need 4 levels of version numbers either.

Just a suggestion to make things easier for the consumers of your software :)

Originally created by @jc21 on GitHub (Feb 10, 2020). Original GitHub issue: https://github.com/bootandy/dust/issues/68 Looking through your release history, your versioning scheme is all over the place. I'm packaging your software on my [Centos](https://yum.jc21.com) and [Debian](https://dpkg.jc21.com) repositories and it's easier for me if the version is of a consistent standard, `v0.0.0`. In these package managers, `v4` is newer than your latest release of `v0.4.5.0`. I would argue that you don't need 4 levels of version numbers either. Just a suggestion to make things easier for the consumers of your software :)
zhus closed this issue 2026-06-08 11:25:22 +03:00
zhus commented 2026-06-08 11:25:22 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Feb 10, 2020):

Hi,

v4 was an accident its version is v0.4.0 and it was marked as a pre-release because of this.

Mostly these things occur as an accident and I can't see how to delete them from github.

Should I drop the 'v' from the versioning? Is that annoying?

<!-- gh-comment-id:584337751 --> @bootandy commented on GitHub (Feb 10, 2020): Hi, v4 was an accident its version is v0.4.0 and it was marked as a pre-release because of this. Mostly these things occur as an accident and I can't see how to delete them from github. Should I drop the 'v' from the versioning? Is that annoying?
zhus commented 2026-06-08 11:25:22 +03:00
Author
Owner
Copy Link
Copy Source

@jc21 commented on GitHub (Feb 11, 2020):

With or without the v is fine and doesn’t matter. It was just a matter of semantic versioning.

<!-- gh-comment-id:584364416 --> @jc21 commented on GitHub (Feb 11, 2020): With or without the v is fine and doesn’t matter. It was just a matter of semantic versioning.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 windows help wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus (Sergey Zhukov)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bootandy/archived-dust#29
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?