alexbrainman
Maintain releases
I faced an issue when I was using this library.
... github.com/alexbrainman/odbc/api/api_unix.go:15:11:
fatal error: 'sql.h' file not found
#include <sql.h>
^~~~~~~
I was using old commit of the master branch. Some one was fixed this and he/her updated the master. So I couldn't catch that and took some time to fix it. This library is very usefull and it is better if you (@alexbrainman) can maintain releases.
Some one was fixed this and he/her updated the master. So I couldn't catch that and took some time to fix it.
What did you do? I would check master branch if I am looking for latest changes of a package.
it is better if you (@alexbrainman) can maintain releases.
What exactly do you propose I do?
Thank you.
Alex
I suggest you to maintain tags updated with proper release notes. Please have a look on this. Thank you @alexbrainman
I suggest you to maintain tags updated with proper release notes.
Last commit was merged nearly year ago. There were 2 commits in the last 2 years. There were 4 commits in the last 3 years.
Do you suggest I tag every commit I merge?
This package code does not change much. So I don't see who would benefit with these tags or release notes.
Alex
Ok, we are using this library with the current development. You introduce new thing to this library or some one fix a bug and you merge that to master branch. How do I identify those changes ?
How do I identify those changes ?
You need to look for these changes on the master branch.
Alex