Open ralfbiedert opened 5 years ago
That is a good idea, however, the problem is that next
had some bugs that needed to be fixed. Also the work was only like 95% done. Bugs are a real concern to me, especially in AI code like this.
While it depends a bit on the Git model used, I don't think that master has to be bug free. I'd argue it only has to be the "main line" of future development, and should compile.
Regarding the bugs, do you remember the problems and could you create issues (even if they might be a bit vague)?
Right now the project looks dead on Github since there wasn't any activity on master for ~1 year, for most code parts even ~2 years.
That makes it hard to attract more developers (or even to explain to your colleagues that the project is not totally abandoned ...)
I think it would make sense to make
next
the newmaster
for better visibility.