Closed fgregg closed 3 years ago
Oh, great question (and I have the same problem 😅).
IIRC, we're maintaining the 0.x series on master because NYC still relies on it, and merging 2.5 would make it difficult to patch bugs to the legacy version. With that said, AFAIK, we don't have a current maintenance agreement for NYC, and package versions are EOL'ed all the time.
So, if we're prepared to say we're no longer developing the 0.x version of django-councilmatic
, then I think we can merge. If not, I'd be fine switching the default branch!
Thoughts, @fgregg?
let's merge!
let's please do this so code search will work, LOL.
it ended up that there were merge conflicts with master. I didn't want to deal with those right now, so I ended up making 2.5 the default branch for github. this addresses the annoyances that we had, I think @hancush
would it be possible to merge the 2.5 branch into master? it would be one less thing for me to remember to do every occasional time I come to this repo?
If we can't do that for some reason, can we make 2.5 the default branch?