Why 2 versions/branches ?

[Mika-6-9]

HI.
Why have two branches for the client: V3.12 and V3.13?
Neither of the last two versions works correctly.
The two versions would have to be merged to have a complete one that works well.
The latest V3.12 has lots of bugs that were fixed with V3.13, but I find it much faster than V3.13.
Looking forward to a V3.14 which merges both and fixes (almost) all the problems

I don't really understand how PRs work with Github, you never really know if the PRs are included in a release or not.
If you implement "enterprise" versions (#6790), you should have a method to better know what is included in a release or not (as for the server with PRs by version, for example: [stable29] or [stable28]) to so that we are not lost.
Thanks

[camilasan]

Why have two branches for the client: V3.12 and V3.13?

Most of the bug fixes atm are backported to 3.12 and 3.13.

I don't really understand how PRs work with Github, you never really know if the PRs are included in a release or not.

You can check the changelog at https://github.com/nextcloud/desktop/releases or the backport request in the PR.

Why have two branches for the client: V3.12 and V3.13?
you should have a method to better know what is included in a release or not (as for the server with PRs by version, for example: [stable29] or [stable28]) to so that we are not lost.

the branches V3.12 and V3.13 you refer to are stable branches like in the server.