On Monday 03 September 2007 10:51, Adrian Schröter wrote:
[Details] "In case the user does not have write permission to the project, a branch of the base project is created by the API."
I would just keep in mind, that a user might want still branch, even if he has write permissions.
[API Calls] It does look that you want alsa allow branching of a complete project. How would that work ?
Yes, branching a project would be POST /source/<project>?cmd=branch
I suppose either
- create new project and create source links for each package
or 2) create a new mechanism which allows linking of projects.
Not sure - needs more discussions ;-)
The "/source/home:<person>/_branchprojects" should maybe
Yes, thats what I meant.
Do you really want to create notifications when branching ? Isn't this something what should get defined later in a generic event notification proposal ? Shouldn't this be called "Merge request notifier" here ?
Probably it should be 'Merge Request'. And I think it needs to be saved somewhere because it holds the information that for a branch project was asked to merge.
Apart from my comments, I think your proposal describes the needed api tasks completely :) We may should also create some end-user workflows dealing with typical use cases to get also a picture what needs to done in the clients.
Yes, next task.
Do you have any opinion how the actual merge should be done ?
Puh - to be honest, I need some input here. From my feeling I doubt that it is possible to do that completely automagically. And I wonder if that is needed - I think that no maintainer will trust an automatic change of his package.
Will it happen in the backend like it happens already when you have source linked + patched packages ?
I have to check that, any opinions on that?