-
Notifications
You must be signed in to change notification settings - Fork 4
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
Near term usage? Registering the package? #20
Comments
I think registration of GraphsOptim.jl would be reasonable, I just wanted to clean up a bit and add more tests but never got around to it |
On the other hand, GraphsFlows and GraphsMatching are bound to be archived because their functionality will land either here or in Graphs.jl |
I'll try to redo the PR merging GraphsFlows into Graphs in the coming days (there was already one but it was unreadable so I'm gonna redo it properly JuliaGraphs/Graphs.jl#329). May I ask you to review it once it's there? |
Happy to help with review |
What is the advice for near term users of this and the flows and matching packages?
Especially in the context of developers. I am comfortable with dealing with deprecations and compatbot PRs for my package. My package will not expose the functionality of these graph packages, only use it internally. Should I depend on the currently available packages or should I politely ask you to register a 0.1.0 version of this package?
The text was updated successfully, but these errors were encountered: