:question: So, here comes the question. As many o...

# ktor

[orangy]

❓
So, here comes the question. As many of you are using ktor in production, should we start doing maintenance branches, like 0.4.x for small bugfixes and 0.5 with new features and may be some API breakages and refactorings? This would certainly slow us down in the course to 1.0, but would make your life may be a little bit easier.
1️⃣ stick to current scheme where there is a single master that is 0.4.x until major API changes are introduced, then switch to 0.5.0
2️⃣ turn on “serious mode” and do maintenance branches with master going towards 0.5
3️⃣ do all work in master targeting 0.5 and only backport fixes into 0.4 branch when it is blocking someone AND it is easy enough to cherry-pick a fix