#1424 Clarifications to Change policy for changes which require rel-eng changes
Closed None Opened 9 years ago by mattdm.

In order to prevent bottleneck/crisis situations which have arisen the last few releases, I want to add to https://fedoraproject.org/wiki/Changes/Policy#Complex_system_wide_changes. Specifically, right under the bit about packaging guidelines in system wide changes, i want to add:

  • For changes which require Release Engineering involvement:
  • please be sure someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook
  • file a [https://fedorahosted.org/rel-eng/newticket ticket] with Release Engineering immediately when the change is accepted, with a detailed breakdown of changes needed
  • work must be substantially complete by Alpha Freeze or the contingency plan will be invoked.

Does this seem good? Any additions or changes?


I personally would rather that release engineering be contacted before the change that people suspect may need Release Enginnering changes is submitted, especially when there is new deliverables, The reason being that we can sit down and work out the best way to integrate it. there has been changes that have written tooling to do a job but we can not use them in our processes. Coming to Release Engineering at Alpha freeze time and saying we need foo is way too late.

Replying to [comment:3 ausil]:

I personally would rather that release engineering be contacted before the change that people suspect may need Release Enginnering changes is submitted, especially when there is new deliverables, The reason being that we can sit down and work out the best way to integrate it. there has been changes that have written tooling to do a job but we can not use them in our processes. Coming to Release Engineering at Alpha freeze time and saying we need foo is way too late.

I think that's ''basically'' what this is meant to say. Minor clarification:

  • For changes which require Release Engineering involvement:
  • Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook
  • File a ​ticket with Release Engineering immediately when the change is accepted, with a detailed breakdown of changes needed
  • Work must be substantially complete and in place by Alpha Freeze or the contingency plan will be invoked.

From today’s FESCo meeting:

AGREED: Clarifications approved (+7)
ACTION: jreznik will update policy process

Login to comment on this ticket.

Metadata