jwakely added a new comment to an issue you are following:
The change proposal template says I need to create a releng ticket and link it to the
* Release engineering: [https://pagure.io/releng/issues
#Releng issue number] (a check of
an impact with Release Engeneering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS
FOR SELF CONTAINED CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to
installer image generation or update package delivery)? Is a mass rebuid required?
include a link to the releng issue.
The issue is required to be filed prior to feature submission, to ensure that someone is
on board to do any process development work and testing, and that all changes make it into
the pipeline; a bullet point in a change is not sufficient communication -->
Maybe I misunderstood what it's telling me.
I will need a side tag, although I don't need it to be created until the change
proposal is approved for F27.
To reply, visit the link below or just reply to this email