Home_greyopenFATE - openSUSE feature tracking > #305899
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Build Service Package Locking

Feature state

Buildservice
Rejected Information

Description

Discussion


icons/user_comment.png P. R. wrote: (8 years ago)

What exactly should lock do? Prevent someone else from checkout ? I think we need better merging mechanism (e.g. replace source backend with git), not locking.

icons/user_comment.png A. S. wrote: (8 years ago)

How would git help here ?

icons/user_comment.png A. S. wrote: (8 years ago)

lock is IMHO the wrong approach. People should submit often, so that other people can follow and can build on top of their changes.
No SCM supports locking afaik for good reasons, the first (accepted) submitter wins and others have to adapt.

So from my point of view, I do not want this feature at all, it hinders more than it helps.

icons/user_comment.png P. R. wrote: (8 years ago)

The problem is with "adapting" you mentioned. Current SCM in buildservice has no merge support, one has to rebase the patches manually, which is PITA.

icons/user_comment.png A. S. wrote: (8 years ago)

osc repairlink is doing a source merge for conflicting changes. You don't even have to do anything for non conflicting changes, if you use a source link.

icons/user_comment.png W. S. wrote: (8 years ago)

Ok consider this withdrawn and look at 305905 insetad.  that way I can add an advisory note to a package before I fix a build failure so other team members won't do the same work in parallel to me.

Last change: 8 years ago
Voting
Score: 2
  • Negative: 0
  • Neutral: 0
  • Positive: 2
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint