#9865 Impact check for https://fedoraproject.org/wiki/Changes/XwaylandStandalone
Closed: Fixed 3 years ago by mohanboddu. Opened 3 years ago by ofourdan.

  • Describe the issue

This change proposal is to build Xwayland as a standalone package built from current git snapshot from upstream git master, separate from the rest of xorg-x11-server packages.

  • When do you need this? (2020/12/29)
    Proposal submission deadline (System Wide Changes)

  • When is this no longer needed or useful? (2021/02/09)

  • If we cannot complete your request, what is the impact?
    We will need to postpone this change request until f35.


I don't understand what is expected of release engineering for this ticket. This sounds like work for the maintainers?

Also, can you give us the change request url?

I don't understand what is expected of release engineering for this ticket. This sounds like work for the maintainers?

I just follow the procedure here https://docs.fedoraproject.org/en-US/program_management/changes_policy/ which states that “For all system-wide changes you must file an issue in releng pagure to check if your change requires Release Engineering involvement.”

Also, can you give us the change request url?

It's in the subject actually, https://fedoraproject.org/wiki/Changes/XwaylandStandalone

The empty template for change proposals https://fedoraproject.org/wiki/Changes/EmptyTemplate also states that “a check of an impact with Release Engineering is needed” hence this ticket.

Issue status updated to: Open (was: Closed)

3 years ago

@ofourdan Thanks for providing the info, now I am able to understand what the change request means, but this doesn't any special work from releng other than reviewing PR's for comps or kickstarts if needed.

Thank you very much for filing the ticket and checking with us.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
- Issue tagged with: change-noreleng, changes, f34, low-gain, low-trouble, ops

3 years ago

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

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Done