Re: Moving to invent.kde.org
> So maybe we can move forward! (if I can suggest anything, I would just make > sure that the repository is set to rebase on master when merging a single > branch to not clutter the history). Sorry for being late, but +1 for gitlab! signature.asc Description: OpenPGP digital signature
Re: Moving to invent.kde.org
Albert Astals Cid ha scritto: > El diumenge, 9 de juny de 2019, a les 20:44:34 CEST, Tobias Deiminger va > escriure: >> >> Branches on private clones could also be a good fit for GSoC. >> Our last years approach to let phabricator track a GSoC branch >> in the central repository caused quite some confusion. > > That's my main aim. > So maybe we can move forward! (if I can suggest anything, I would just make sure that the repository is set to rebase on master when merging a single branch to not clutter the history). Ciao -- Luigi
Re: Moving to invent.kde.org
El diumenge, 9 de juny de 2019, a les 20:44:34 CEST, Tobias Deiminger va escriure: > Am 09.06.2019 12:13 schrieb Albert Astals Cid: > > El diumenge, 9 de juny de 2019, a les 11:06:43 CEST, Tobias Deiminger > > va escriure: > >> Am 08.06.2019 11:22 schrieb Albert Astals Cid: > >> > How would you feel if we moved to invent.kde.org now instead of > >> > waiting for the final migration? > >> > >> If that means we'll gain a pure gitlab workflow (merge requests, > >> issues, > >> CI), I'd like it, the sooner the better. > > > > No issues, bugzilla is here to stay. > > > > CI is still being discussed, as far as i understand build.kde.org is > > still the way to go, which shold be fine, it works just fine for us. > > kdenlive has per MR CI builds, e.g.: > https://invent.kde.org/thompsony/kdenlive/-/jobs/8072 > > Will we get that too? (guess it can be complementary to what > build.kde.org does) I don't see why we would not be able to get something that kdenlive has. > > > So this is basically more about MR (and the fact that you can easily > > fork and thus have branches on "your own repo" where you can force > > push) > > Good thing. > > Branches on private clones could also be a good fit for GSoC. > Our last years approach to let phabricator track a GSoC branch > in the central repository caused quite some confusion. That's my main aim. Cheers, Albert > > >> > >> Are there downsides? > >> > >> > The bigger chance would be that "future" code reviews would be done > >> > through gitlab instead of through phabricator. > >> > >> What about phabricator reviews that are currently in progress, are > >> there > >> conversion scripts or will we have to resubmit them as MRs? > > > > They can stay AFAIK. I mean as far as i understand you can put > > "anything you want" in phabricator, so if the git repository moves > > somewhere else it doesn't really matter. > > After all, and if migration doesn't mean additional load on your side, > I'd still vote for doing it. > > Cheers > Tobias >
Re: Moving to invent.kde.org
Am 09.06.2019 12:13 schrieb Albert Astals Cid: El diumenge, 9 de juny de 2019, a les 11:06:43 CEST, Tobias Deiminger va escriure: Am 08.06.2019 11:22 schrieb Albert Astals Cid: > How would you feel if we moved to invent.kde.org now instead of > waiting for the final migration? If that means we'll gain a pure gitlab workflow (merge requests, issues, CI), I'd like it, the sooner the better. No issues, bugzilla is here to stay. CI is still being discussed, as far as i understand build.kde.org is still the way to go, which shold be fine, it works just fine for us. kdenlive has per MR CI builds, e.g.: https://invent.kde.org/thompsony/kdenlive/-/jobs/8072 Will we get that too? (guess it can be complementary to what build.kde.org does) So this is basically more about MR (and the fact that you can easily fork and thus have branches on "your own repo" where you can force push) Good thing. Branches on private clones could also be a good fit for GSoC. Our last years approach to let phabricator track a GSoC branch in the central repository caused quite some confusion. Are there downsides? > The bigger chance would be that "future" code reviews would be done > through gitlab instead of through phabricator. What about phabricator reviews that are currently in progress, are there conversion scripts or will we have to resubmit them as MRs? They can stay AFAIK. I mean as far as i understand you can put "anything you want" in phabricator, so if the git repository moves somewhere else it doesn't really matter. After all, and if migration doesn't mean additional load on your side, I'd still vote for doing it. Cheers Tobias
Re: Moving to invent.kde.org
El diumenge, 9 de juny de 2019, a les 11:06:43 CEST, Tobias Deiminger va escriure: > Am 08.06.2019 11:22 schrieb Albert Astals Cid: > > How would you feel if we moved to invent.kde.org now instead of > > waiting for the final migration? > > If that means we'll gain a pure gitlab workflow (merge requests, issues, > CI), I'd like it, the sooner the better. No issues, bugzilla is here to stay. CI is still being discussed, as far as i understand build.kde.org is still the way to go, which shold be fine, it works just fine for us. So this is basically more about MR (and the fact that you can easily fork and thus have branches on "your own repo" where you can force push) > > Are there downsides? > > > The bigger chance would be that "future" code reviews would be done > > through gitlab instead of through phabricator. > > What about phabricator reviews that are currently in progress, are there > conversion scripts or will we have to resubmit them as MRs? They can stay AFAIK. I mean as far as i understand you can put "anything you want" in phabricator, so if the git repository moves somewhere else it doesn't really matter. Cheers, Albert > > > Cheers, > > Albert > > Cheers > Tobias >
Re: Moving to invent.kde.org
Am 08.06.2019 11:22 schrieb Albert Astals Cid: How would you feel if we moved to invent.kde.org now instead of waiting for the final migration? If that means we'll gain a pure gitlab workflow (merge requests, issues, CI), I'd like it, the sooner the better. Are there downsides? The bigger chance would be that "future" code reviews would be done through gitlab instead of through phabricator. What about phabricator reviews that are currently in progress, are there conversion scripts or will we have to resubmit them as MRs? Cheers, Albert Cheers Tobias
Re: Moving to invent.kde.org
El dissabte, 8 de juny de 2019, a les 15:24:49 CEST, Philippe Cayzelle va escriure: > Hye, how can i unsuscribe from this newsletter ? Thanks The same way you subscribed to it. Cheers, Albert > > Philippe > > Le sam. 8 juin 2019 à 11:22, Albert Astals Cid a écrit : > > > How would you feel if we moved to invent.kde.org now instead of waiting > > for the final migration? > > > > The bigger chance would be that "future" code reviews would be done > > through gitlab instead of through phabricator. > > > > Cheers, > > Albert > > > > > > >
Re: Moving to invent.kde.org
Hye, how can i unsuscribe from this newsletter ? Thanks Philippe Le sam. 8 juin 2019 à 11:22, Albert Astals Cid a écrit : > How would you feel if we moved to invent.kde.org now instead of waiting > for the final migration? > > The bigger chance would be that "future" code reviews would be done > through gitlab instead of through phabricator. > > Cheers, > Albert > > >
Moving to invent.kde.org
How would you feel if we moved to invent.kde.org now instead of waiting for the final migration? The bigger chance would be that "future" code reviews would be done through gitlab instead of through phabricator. Cheers, Albert
