| 2023-04-20 14:37:48 |
Robie Basak |
description |
In some cases, Ubuntu developers need to close or otherwise manipulate the status of MPs that have been filed against git-ubuntu targets, but are unable to do so.
For example, an Ubuntu developer who can upload the package in question might want to mark an unsuitable MP filed by a third party contributor as Rejected.
But since they cannot push to that branch directly, Launchpad does not allow them to do so.
In another example, in https://code.launchpad.net/~utkarsh/ubuntu/+source/libyang2/+git/libyang2/+merge/435585, the upload is no longer required as the change was synced from Debian, but apparently the submitter of the MP (who can upload this package) only has options to change the status to Work in progress, Needs review, Approved or Merged. |
In some cases, Ubuntu developers need to close or otherwise manipulate the status of MPs that have been filed against git-ubuntu targets, but are unable to do so.
For example, an Ubuntu developer who can upload the package in question might want to mark an unsuitable MP filed by a third party contributor as Rejected.
But since they cannot push to that branch directly, Launchpad does not allow them to do so.
In another example, in https://code.launchpad.net/~utkarsh/ubuntu/+source/libyang2/+git/libyang2/+merge/435585, the upload is no longer required as the change was synced from Debian, but apparently the submitter of the MP (who can upload this package) only has options to change the status to Work in progress, Needs review, Approved or Merged.
More examples:
https://code.launchpad.net/~kobako/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/441282/comments/1173859 |
|
| 2023-05-25 12:26:21 |
Robie Basak |
description |
In some cases, Ubuntu developers need to close or otherwise manipulate the status of MPs that have been filed against git-ubuntu targets, but are unable to do so.
For example, an Ubuntu developer who can upload the package in question might want to mark an unsuitable MP filed by a third party contributor as Rejected.
But since they cannot push to that branch directly, Launchpad does not allow them to do so.
In another example, in https://code.launchpad.net/~utkarsh/ubuntu/+source/libyang2/+git/libyang2/+merge/435585, the upload is no longer required as the change was synced from Debian, but apparently the submitter of the MP (who can upload this package) only has options to change the status to Work in progress, Needs review, Approved or Merged.
More examples:
https://code.launchpad.net/~kobako/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/441282/comments/1173859 |
In some cases, Ubuntu developers need to close or otherwise manipulate the status of MPs that have been filed against git-ubuntu targets, but are unable to do so.
For example, an Ubuntu developer who can upload the package in question might want to mark an unsuitable MP filed by a third party contributor as Rejected.
But since they cannot push to that branch directly, Launchpad does not allow them to do so.
In another example, in https://code.launchpad.net/~utkarsh/ubuntu/+source/libyang2/+git/libyang2/+merge/435585, the upload is no longer required as the change was synced from Debian, but apparently the submitter of the MP (who can upload this package) only has options to change the status to Work in progress, Needs review, Approved or Merged.
More examples:
https://code.launchpad.net/~kobako/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/441282/comments/1173859
Status update: once the staging function is implemented (https://discourse.ubuntu.com/t/spec-git-ubuntu-staged-uploads/35409), then MPs will be able to be filed against the staging branches (eg. pkg/next/ubuntu/devel) and so we will change to doing that instead of filing MPs against the importer branches. Any person who can upload a package will be able to push to the corresponding staging branches. I believe that this means that MPs will be fully manipulatable by uploaders of the corresponding package, which should sufficiently resolve this issue. |
|
