- edited description
- changed title to Add changelog links
Add changelog links
Issue #11
new
It would be helpful to have a direct link to the changelog on the package page.
For stripe (https://www.versioneye.com/python/stripe) this would be https://github.com/stripe/stripe-python/blob/master/CHANGELOG
For boto (https://www.versioneye.com/python/boto) this would be http://docs.pythonboto.org/en/latest/#release-notes
For djangorestframework (https://www.versioneye.com/python/djangorestframework) this would be http://www.django-rest-framework.org/topics/release-notes/
For newrelic (https://www.versioneye.com/python/newrelic) this would be https://docs.newrelic.com/docs/release-notes/agent-release-notes/python-release-notes
Comments (17)
-
reporter
-
reporter
- edited description
-
reporter
- edited description
-
Good idea. Currently we are not crawling & parsing Changelogs systematically, but it's on the Roadmap, together with Security.
-
reporter
It is tricky to parse it automatically, it seems that each library has a different location (if they have) where you can find the changelog.
Do you add the changelogs manual, so should I continue providing the changelog locations? Or do you wait/prefer the automatic way?
-
+1 That would be great! Maybe just let the community add links for that?
-
Robert, what about integration between VersionEye and AllMyChanges? My service is damn good in release notes parsing and is able to take data from different sources.
I see this integration a a win-win, because VersionEye will fill AllMyChanges with new user and packages and AllMyChanges could show release notes in VesionEye through API.
-
That sounds like a good idea. Does AllMyChanges has an public API?
-
It has an API, but it is not documented. I have to work on documentation to make it more usable.
Do you have some vision about the way our services could be integrated together?
-
This would be an awesome feature! Everytime I receive an update email I need to follow the links to github and search for the changelog there... So this would be much appreciated!
-
What I'm thinking about as an alternative to having direct links to changelogs at versions eye, is integration of allmychanges with versioneye, where you bind them together, and allmychanges will send you release notes of packages you are following at versioneye.
What are you thinking about this, guys!?
-
I like the idea. Ping me again next week. I have 3 weddings this week and some other tasks to do.
-
Ok.
-
This is a GREAT idea, because on each update I have to hunt down the changelog to see if I should update it. (I was going to start a new issue, but found this.)
Howover, as mentioned, they all have different name: https://github.com/restify/node-restify/blob/master/CHANGES.md https://github.com/petkaantonov/bluebird/blob/master/changelog.md ... and I've seen some places call it history.md And many others don't have it at all and I have to try to read the commit log.
One idea: parse in package.json (for npm at least) a "changes" link to a file, which will be auto-linked? If that could be standardized into a format that would be pretty cool, but sounds even harder...
-
Signed up and started following stuff in allmychanges, but it has VERY few packages already tracked... so I'm adding them now.
OK now that I read the thread a bit more it seems allmychanges is already built more specifically for this and already parses the versions from the changelog.
-
Avi, I've seen your activity at allmychanges. Thank you for adding more packages. Hope, I'll add more tight integration with GitHub and VersionEye soon.
-
Seems to be duplicated by: https://bitbucket.org/versioneye/versioneye/issues/168/versions-should-link-to-the-github-tag
- Log in to comment
