anitya icon indicating copy to clipboard operation
anitya copied to clipboard

Allow projects to specify CHANGELOG location

Open ralphbean opened this issue 10 years ago • 6 comments

It would be cool if we could have some kind of link or specification of where the changelog lives for each project.

Opportunities:

  • We could include some kind of pointer to the changelog in the fedmsg payload.
  • We could then have the-new-hotness daemon try to extract the changelog snippet for the latest release and add it to the bugzilla ticket.
  • FMN notifications about new upstream releases could include the changelog snippet in the long_form representation.
  • This would help packagers more quickly understand if the latest release if something that should be looked at more closely (or if any additional steps should be taken).

Maybe we could use pandoc for parsing at an additional step down the pipeline.

Problems:

  • Some projects don't have a changelog at all, so we need to handle that.
  • Some projects keep their changelog as HTML on their site, but it is not included in their tarball.
  • Some projects keep their changelog in their source control repo, but it is not included in their tarball.
  • Some projects keep it in their tarball.

I don't immediately see a way to allow anitya maintainers to easily specify the location, accounting for all those possibilities. Will have to think about how best to add this to the db model.

/cc @vdanen

ralphbean avatar Dec 03 '15 16:12 ralphbean

This would also be something https://github.com/flathub/flatpak-external-data-checker would like to consume

razzeee avatar May 09 '23 07:05 razzeee

What needs to be done:

  • Add new field to project page that allows you to add link to changelog
  • Add new filed to Anitya message schema
  • Update the-new-hotness to work with this new message field

For now I would ignore any project that doesn't have changelog on URL.

Zlopez avatar May 15 '23 13:05 Zlopez

It would be great, if it could not only consume changelog files, but also github(or else) releases

razzeee avatar May 15 '23 13:05 razzeee

@razzeee In this case, it will be just enough to add link to Github releases page.

Zlopez avatar May 15 '23 14:05 Zlopez

Yes, but I would also expect anitya to then filter these down and add the correct release notes to the correct release. Did I get that right?

razzeee avatar May 15 '23 14:05 razzeee

Maybe this could be an improvement, but in the first iteration just adding changelog link should be enough.

Zlopez avatar May 15 '23 14:05 Zlopez