Closed tlepoint closed 8 years ago
Indeed, we should do a release. Maybe after we merge the PR for serialization ?
When you talk of package managers you are thinking of a specific automated process ?
I was thinking of classical packages managers (apt-get, pacman, brew, macports, etc.).
That can be a good idea indeed :) What can be done on github is to tag a specific commit in the master branch, and tell github that this is a release : https://help.github.com/articles/creating-releases/
@tlepoint I completely agree that would be great. What I was asking was if we could automate the process so that each time we make a release packages for classic package managers could be added automatically.
In any case I agree for releases and for packages.
One question @tlepoint you were thinking about source packages (that will once installed allow the user to compile NFLlib) or binary packages ?
I meant was Adrien said, tag a version as a release. I am not particularly in favor of proposing binary packages on a website. Whether it will be included in some package managers, either compiled or not, is something I find orthogonal.
Well I am ok then for releases.
Version 1.0.0 after the PR is merged?
Yes go ahead !
Hi,
What do you think of doing releases of NFLlib (so that it could be handle by package managers)?