Development process change

Hello everyone,

In the coming days, I’m going to change the development process of Paperwork. Fear not ! It’s about to become much simpler !

Basically, I’m going switch from my variant of GitFlow to OneFlow.

The GitFlow variant made sense at the time: Paperwork 1.x was the public version (branch master), and at the same time I was actively working on Paperwork 2.0. I needed feedback on 2.0, and therefore I needed a branch develop with CI/CD pushing to a Flatpak branch. Also, later versions (2.1, 2.2) included some pretty heavy changes, and I preferred having a translation/testing phase → I made Weblate push the translations on the branch testing.

Now there are AppImages built on all branches, making it easier to test them. Morever, the testing and develop branches have become more of a burden for me (a lot of merges and cherry-pick to do all the time) and a source of confusion for contributors.

So in the coming days, I will merge develop and testing as is in master (there are little to no differences at the moment between them). I will point Weblate to the branch master. And every contributions from then on will go directly to the branch master.

Please let me know if you have any questions.