Skip to content
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.

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

Future of ctn_benchmarks #10

Open
jgosmann opened this issue May 31, 2016 · 0 comments
Open

Future of ctn_benchmarks #10

jgosmann opened this issue May 31, 2016 · 0 comments
Labels

Comments

@jgosmann
Copy link
Collaborator

Because development activity seems to be slightly increasing here (#8, #9), I was wondering what the plans for the future are, especially with respect to PR #7. As #7 is a major rewrite of central parts it seems that it might be wasted effort to implement a lot of new features on the current master branch if the intend is to transition to that approach. It certainly adds complexity, but also increases the flexibility.

I will use #7 as part of my projects for sure and it would be nice to be able to link to it and pip install it easily (which is problematic if it lives in this branch). So if there is no intend to get this merged into ctn_benchmarks, I might go ahead and transition the code from the PR to its own repository.

Another point is that I think that #4 should be resolved earlier than later. The larger the user-base, the more problematic such fundamental changes as renaming the package will get.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant