rpkg

#136 Better notification of new release of rpkg and fedpkg to let upstream know what is the latest changes
Closed: Fixed Opened by cqi.

Closed: Fixed
Reopen Issue

Currently, when release a new version of rpkg and fedpkg, just make new RPMs in Koji and create new update in Bodhi, then waiting for users to test it, and pushed to Stable finally when everything works well. So, what else could we do so that larger scope of users in Fedora community could know the latest changes?

So far, what I can figure out may contains

  • sending email to devel@lists.fedoraproject.org. What other mailing list?
  • using a changelog file to document the changes of each release in the history. This would be convenient way for users or developers to query the changes in the past.
  • publish a documentation site for rpkg and fedpkg, that is not only for documentation, but also for a place to publish the changelog of each release.
  • simply update changelog in dedicated wiki page in Fedora Project Wiki for rpkg and fedpkg individually.

Not all of above we have to do, but they are good ways in practice, and not too difficult to do them. What else could we do? Any thought?

For inspiration new releases of mock are announced on buildsys@ mailing list:
https://lists.fedoraproject.org/archives/list/buildsys@lists.fedoraproject.org/thread/UTLVW5G6BEOA6UQLMWFXNCM3QXZMKCBT/

:thumbsup: meanwhile, the mail could go to devel mailing list and just after the new update created in Bodhi.

Metadata Update from @cqi:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None

RFE

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.