Closed doctrinebot closed 4 years ago
This is obviously the "usual mess" - we haven't used merge-up strategy so far, so this patch is clear conflict with everything in the 2.0
branch
Note: branch 1.4.x
does not exist at this point in time, but many milestone items are already in it: need to discuss branching strategy on this particular repository.
2.0 had its last activity 2 years ago, so I'd say we disregard that for now. master
currently is 1.4.x-dev
and has been used as such.
For the time being, I'd close this PR and re-analyse the 2.0 branch to see if we can pick up the work again.
Renaming 2.0
to next
(both branch and milestone) could also make things more manageable for the time being
2.0
branch re-pushed as next
as to not confuse our bot. Closing here.
Release 1.3.3
1.3.3
Improvement