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

About 4.1.6 #10041

Open
sledgehammer999 opened this Issue Dec 24, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@sledgehammer999
Copy link
Contributor

sledgehammer999 commented Dec 24, 2018

@qbittorrent/demigods Here are my thoughts on the next version

IMO, the v4.1.x series are quite stable. As of now, they enter maintenance mode.
This means that only fixes go into the v4_1_x branch. If you submit an important fix in master that needs backporting then you are responsible to open a PR that backports it in the v4_1_x branch too.
For fixes that are submitted by other people who don't want to make a backporting PR there are 2 possible solutions. Either someone else takes the responsibility to open a backporting PR or that PR is entered in the list below for me to backport before a possible 4.1.6 release.
(aka I want to lessen the load on myself for the maintenance release).

Due to the above, we are now allowed to "break" compatibility between master and v4_1_x. For example, increase c++ mode to c++14, drop the RC_1_0 support even before the RC_1_2 support is finished, possibly raise Qt minimum version if needed, drop deprecated code, drop Windows Vista and below support etc.
Caution: Don't use this issue to discuss what happens in master. Open a new one.

Edit this list to add new PR numbers that need backporting by me for 4.1.6

List of PRs that need backporting

@glassez

This comment has been minimized.

Copy link
Member

glassez commented Dec 25, 2018

increase c++ mode to c++14, drop the RC_1_0 support even before the RC_1_2 support is finished, possibly raise Qt minimum version if needed, drop deprecated code, drop Windows Vista and below support etc.

👍

@glassez

This comment has been minimized.

Copy link
Member

glassez commented Dec 25, 2018

Qt 5.12 is LTS. We can stick to it in v4.2.x.

@sledgehammer999, we need to discuss and then declare minimal supported versions of tools and libraries for 4.2 branch. Can you open an appropriate Issue?

@Chocobo1

This comment has been minimized.

Copy link
Member

Chocobo1 commented Dec 26, 2018

TravisCI on 4.1.x is broken, havn't got time to look into.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment