8000 Make 0.5 master, and 0.4 a branch for better visibility. · Issue #11 · Robbepop/prophet · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Make 0.5 master, and 0.4 a branch for better visibility. #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ralfbiedert opened this issue Aug 16, 2019 · 2 comments
Open

Make 0.5 master, and 0.4 a branch for better visibility. #11

ralfbiedert opened this issue Aug 16, 2019 · 2 comments

Comments

@ralfbiedert
Copy link

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 new master for better visibility.
@Robbepop
Copy link
Owner

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.

@ralfbiedert
Copy link
Author

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)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ralfbiedert @Robbepop
0