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.

Sign up for GitHub

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

Jump to bottom

Request: Start using semantic versioning starting from 4.0 release #1037

Closed
0x022b opened this issue Nov 3, 2019 · 3 comments · Fixed by #3867
Closed

Request: Start using semantic versioning starting from 4.0 release #1037

0x022b opened this issue Nov 3, 2019 · 3 comments · Fixed by #3867
Labels
confirmed
Milestone
4.0.0-beta.1

Comments

@0x022b
Copy link

0x022b commented Nov 3, 2019

I think Transmission should start using semantic versioning starting from next major release to make it easier for end users, developers and package maintainers to see which versions are bug fix releases and which ones include new functionality.

You can read more about semantic versioning from here.
@Arcitec
Copy link

Arcitec commented Jan 26, 2020

Fantastic idea. YES!

@ckerr
Copy link
Member

ckerr commented Jan 25, 2022

I like this idea. We're obviously too late for 3.0, but rather than being in 3.xx limbo forever I think we're going to skip to v4 for the next release due to all of the rewriting that's taken place over the last 3-4 months as a result of switching from C to C++. That seems like a good time to switch to semver.

@Arcitec
Copy link

Arcitec commented Jan 26, 2022

@ckerr Great, I agree! :)

@ckerr ckerr changed the title Request: Start using semantic versioning starting from 3.0 release Request: Start using semantic versioning starting from 4.0 release Jan 26, 2022
@ckerr ckerr added this to the 4.0.0-beta.1 milestone Feb 24, 2022
ckerr added a commit that referenced this issue Oct 3, 2022
@ckerr
build: semver versioning
ab18d19 
Xref: #1037
@ckerr ckerr mentioned this issue Oct 3, 2022
Merged
ckerr added a commit that referenced this issue Oct 5, 2022
@ckerr
build: semver versioning
4a57cf5 
Xref: #1037
ckerr added a commit that referenced this issue Oct 5, 2022
@ckerr @mikedld
build: support semver versioning (#3867)
89d6533 
* build: semver versioning

Xref: #1037

* test: add base62 tests for client-id

* build: include PATCH_VERSION in Transmission.rc.in

* build: semver versioning in version.h

* fixup! build: semver versioning in version.h

undo experimental verison changes that were made for testing purposes

* Fixup version in MSI package filename

Co-authored-by: Mike Gelfand <mikedld@mikedld.com>
@ckerr ckerr mentioned this issue Feb 13, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
confirmed
Milestone
4.0.0-beta.1
Development

Successfully merging a pull request may close this issue.

build: support semver versioning transmission/transmission
3 participants
@ckerr @0x022b @Arcitec