- 🇩🇪Germany Grevil
I think creating 2.x-dev already without actually working on it was a big mistake and results in irritation, when choosing the correct version to work on.
Furthermore, every single commit to 1.2.x has to be cherry-picked in to 2.x
- 🇩🇪Germany Anybody Porta Westfalica
@Grevil: Yeah that's PM vs. Code. It's super helpful for issue structuring, but bad for code. I don't see an easy way to handle it. We could just remove all code from 2.x and put a readme in place. One day we then copy the 1.x contents over again, when starting to work in 2.x?
Guess there were no code changes yet?
- 🇩🇪Germany Grevil
@Anybody possible, but that wouldn't help with selecting the right version. Let's simply keep it like this for now.
- 🇩🇪Germany Grevil
2.x now differs from 1.2.x. There were a couple of issues only merged for 1.2.x. We should reset 2.x on the status of 1.2.x once its time.