[New: openFATE 310974] Prevent work on package if there are submissions
Feature added by: Andreas Jaeger (a_jaeger) Feature #310974, revision 1 Title: Prevent work on package if there are submissions Buildservice: New Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Product Manager: (Novell) Project Manager: (Novell) Partner organization: openSUSE.org Description: Currently a packager that works on a package might change it and a person that branched the package previously has already some changes done and those might break with the changes in the project. We need better support for these situations. -- openSUSE Feature: https://features.opensuse.org/310974
Feature changed by: Sascha Peilicke (saschpe) Feature #310974, revision 2 Title: Prevent work on package if there are submissions Buildservice: New Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Product Manager: (Novell) Project Manager: (Novell) Partner organization: openSUSE.org Description: Currently a packager that works on a package might change it and a person that branched the package previously has already some changes done and those might break with the changes in the project. We need better support for these situations. + Discussion: + #1: Sascha Peilicke (saschpe) (2010-12-17 15:46:16) + The last submitter to the package has to solve collisions, simply. Like + you have to do it with any SCM. + What we may want to improve is the means to communicate between users + that work on the same package or to get notified more prominently about + progress in package branches. But those are mostly social issues then :- + ) -- openSUSE Feature: https://features.opensuse.org/310974
Feature changed by: Sascha Peilicke (saschpe) Feature #310974, revision 3 Title: Prevent work on package if there are submissions - Buildservice: New + Buildservice: Rejected by Sascha Peilicke (saschpe) + reject reason: Merge conflicts always happen. Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Product Manager: (Novell) Project Manager: (Novell) Partner organization: openSUSE.org Description: Currently a packager that works on a package might change it and a person that branched the package previously has already some changes done and those might break with the changes in the project. We need better support for these situations. Discussion: #1: Sascha Peilicke (saschpe) (2010-12-17 15:46:16) The last submitter to the package has to solve collisions, simply. Like you have to do it with any SCM. What we may want to improve is the means to communicate between users that work on the same package or to get notified more prominently about progress in package branches. But those are mostly social issues then :- ) -- openSUSE Feature: https://features.opensuse.org/310974
Feature changed by: Adrian Schröter (adrianSuSE) Feature #310974, revision 4 Title: Prevent work on package if there are submissions Buildservice: Rejected by Sascha Peilicke (saschpe) reject reason: Merge conflicts always happen. Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Product Manager: (Novell) Project Manager: (Novell) Partner organization: openSUSE.org Description: Currently a packager that works on a package might change it and a person that branched the package previously has already some changes done and those might break with the changes in the project. We need better support for these situations. Discussion: #1: Sascha Peilicke (saschpe) (2010-12-17 15:46:16) The last submitter to the package has to solve collisions, simply. Like you have to do it with any SCM. What we may want to improve is the means to communicate between users that work on the same package or to get notified more prominently about progress in package branches. But those are mostly social issues then :- ) + #2: Adrian Schröter (adriansuse) (2011-01-31 10:07:30) + Yes, fully agree with Sascha. However, we could rephrase this request + maybe as "Show better active current work on a certain package.". + We have a first step here by showing branched packages. A second step + would maybe to give some overview when they got created and which + version is inside. -- openSUSE Feature: https://features.opensuse.org/310974
participants (1)
-
fate_noreply@suse.de