From Fedora Project Wiki

(initial version)
 
mNo edit summary
Line 14: Line 14:
Currently when a packager wants to adopt a package that was previously orphan he needs to file a ticket for releng to process the requests (example : https://pagure.io/releng/issues?status=Closed&search_pattern=orphan)
Currently when a packager wants to adopt a package that was previously orphan he needs to file a ticket for releng to process the requests (example : https://pagure.io/releng/issues?status=Closed&search_pattern=orphan)


Then a releng engineer needs to manually perform the following checks :
The following need to be true for a package to be sucessfully adopted.
 
* the package is not retired
* the package is actually orphaned
* the package is orphaned for less than 2 weeks
* the person adopting the package is in the packager FAS group
 
When all these conditions are meet the following script can be use to give the package https://pagure.io/releng/blob/master/f/scripts/distgit/give-package.py

Revision as of 20:00, 28 January 2019

Release Engineering Automation

This is a working document that aims to identify and breakdown the work needed to automate most of Fedora Release engineering.

Release Engineering Tasks that would benefit from automation

  • Adopting a package
  • TBD

Adopting a package

Currently when a packager wants to adopt a package that was previously orphan he needs to file a ticket for releng to process the requests (example : https://pagure.io/releng/issues?status=Closed&search_pattern=orphan)

The following need to be true for a package to be sucessfully adopted.

  • the package is not retired
  • the package is actually orphaned
  • the package is orphaned for less than 2 weeks
  • the person adopting the package is in the packager FAS group

When all these conditions are meet the following script can be use to give the package https://pagure.io/releng/blob/master/f/scripts/distgit/give-package.py