On Fri, Jan 11, 2019 at 11:23 AM Danylo Piliaiev <danylo.pilia...@gmail.com> wrote:
> My small thoughts/questions: > > - First of all discussions are really much more convenient. > - Several (mine) merge requests were "Closed" and merged (not just merged, > they are under "Closed" category), am I missing something? > It depends on how it's merged. My preference (and I would recommend this to others) is to have the submitter check the "Allow commits from members who can merge to the target branch." check box and then use the web UI to rebase and merge. Then the merge request shows up under "merged" instead of "closed". What some other people have taken to doing is to just push the changes to master and then close the MR. It also works but I think it's probably more confusing to submitters. > - Is there a way to grant rights to creator of merge request to add/change > tags if he doesn't have "Developer" role? > I'm not sure. > - Maybe adding more tags/more granular tags would be a good idea. > - Could Intel CI be integrated in some way with gitlab? > > Overall as someone who didn't interact with mailing lists workflow much > Gitlab is definitely a win. > > On 1/11/19 6:57 PM, Jason Ekstrand wrote: > > All, > > The mesa project has now hit 100 merge requests (36 are still open). I > (and I'm sure others) would be curious to hear people's initial thoughts on > the process. What's working well? What's not working? Is it total fail > and should we go back to mailing lists? > > --Jason > > > > _______________________________________________ > mesa-dev mailing > listmesa-dev@lists.freedesktop.orghttps://lists.freedesktop.org/mailman/listinfo/mesa-dev > > >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
