#3 Integration of Anitya to Packager Workflow
Closed 3 years ago by amoloney. Opened 3 years ago by zlopez.

New initiative: Integration of Anitya to Packager Workflow

What is this initiative about?

The purpose of this initiative is automatic project creation in Anitya for every new package added to Fedora. This needs the following changes:

  • API in Anitya for creating new project and mapping (already done)

  • Way to provide requested information for new project in Anitya when requesting a new repository for fedora package (this will probably need some coordination with rel-eng team)

  • Automatic script that will take the information above and call the Anitya API

Why this initiative?

The Anitya is used as a tracker for new releases for plenty of Fedora packages and this initiative should make it even more usable for Fedora packagers.

Definition of success

What is the minimal outcome you would like to see from this initiative to be satisfied?
Minimal outcome is everything in the What section

What are your nice or really nice to have wishes?
There are few things I would consider really nice:

  • Web form for requesting a new package and where the information for Anitya could be filled
  • API for the above web forms, so the process could be automated
  • EPEL, modules support (this needs changes in the-new-hotness)

Area/community impacted

This initiative will impact all new Fedora packagers


Do this initiative have any dependencies? No, everything should be already in place
Skills needed? Rel-eng, Anitya
Person who must or should be involved? Me
Other work that should be completed prior to this initiative? None


Is this initiative under a time-constraint? Should it start or end before a certain date?
No deadline for this initiative

After CPE team review, this proposal has been re-filed under Releng tracker as an RFE - Request for Enhancement.

New ticket can be viewed here: https://pagure.io/releng/issue/10110

This proposal will be closed.

Metadata Update from @amoloney:
- Issue status updated to: Closed (was: Open)

3 years ago

Issue status updated to: Open (was: Closed)

3 years ago

Metadata Update from @amoloney:
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.