Blocking Issues and Features for GNOME Migration to GitLab

changed the description

changed title from Blocking Bugs for GNOME Migration to GitLab to Blocking Bugs and Features for GNOME Migration to GitLab

changed the description

@eliran.mesika : Can you make sure we've captured everything we need for GNOME on this issue? I.e. we've captured all the requirements we've chatted to them about.

cc @smcgivern

@smcgivern : I don't think we have an issue for moving FF to CE right? Can you confirm?

changed milestone to %Next 2-3 months in gitlab-foss

marked this issue as related to gitlab-foss#24945 (closed)

marked this issue as related to gitlab-foss#31847 (moved)

marked this issue as related to gitlab-foss#33770 (closed)

marked this issue as related to gitlab-foss#34284 (moved)

marked this issue as related to gitlab-foss#27031 (moved)

@victorwu I think it's one of our most popular issues! https://gitlab.com/gitlab-org/gitlab-ce/issues/20076

Ah yes. Moving a popular feature to CE would of course be a popular issue. Updating here. Thanks.

changed the description

marked this issue as related to gitlab-foss#20076 (closed)

Hi all,

Great to hear the news about GNOME - particularly as it sounds like they plan to use a ff-only workflow that sounds very similar to the one my company has been using on gitlab for almost a year now. I hope no one minds me commenting in this way, but it seems likely GNOME will run into the same issues that frustrate our users; could I suggest these issues might be relevant too:

https://gitlab.com/gitlab-org/gitlab-ee/issues/1774 (the title for this one could be misleading; a better summary might be 'when rebase operation fails users are not told the rebase has failed or why'.

https://gitlab.com/gitlab-org/gitlab-ee/issues/895 (this is a really frustrating usability issue)

Hope that's helpful.

Actually maybe I got the wrong idea and GNOME don't intend to use the 'rebase' feature within GitLab? If not those two aren't relevent and you can ignore me. :-)

changed title from Blocking Bugs and Features for GNOME Migration to GitLab to Blocking Issues and Features for GNOME Migration to GitLab

changed the description

@victorwu these are all the issues they noted to me, yes.

@eliran.mesika how's this going? I saw this was linked from the GNOME GitLab :)

@connorshea trying to move the issues along within the respective ones.

mentioned in issue gitlab-foss#31847 (moved)

@connorshea @eliran.mesika : This is our meta issue to track the GNOME blockers.

We are working on https://gitlab.com/gitlab-org/gitlab-ce/issues/20076 for 10.1

@smcgivern : I think we can roughly plan to get https://gitlab.com/gitlab-org/gitlab-ce/issues/31847 going for 10.2. Does that sound about right to you? Then we'll be really close to wrapping all the requests here.

@victorwu yes, with the caveat that 10.2 is interrupted a little because of the summit.

mentioned in issue gitlab-foss#34284 (moved)

@victorwu:

Will https://gitlab.com/gitlab-org/gitlab-ce/issues/24945 make 10.1?
What is the plan for https://gitlab.com/gitlab-org/gitlab-ce/issues/34284?

Regarding gitlab-foss#31847 (moved), my plan with GNOME is to announce their adoption of GitLab in November so assuming we'll be on plan there any delays will be very problematic as that FF will be part of the message as well as needs of the community.

@victorwu @JobV some clarifications from GNOME: critical projects won't be able to move until https://gitlab.com/gitlab-org/gitlab-ce/issues/24945 and https://gitlab.com/gitlab-org/gitlab-ce/issues/31847 will be resolved. This means our announcement won't happen until the critical projects have been migrated to GitLab. Can we prioritize these two issues accordingly?

FYI, GNOME has a dedicated issues for bugs or missing features/details they are keeping on their new instance: https://gitlab.gnome.org/GNOME/Infrastructure/issues/8

changed the description

@eliran.mesika : https://gitlab.com/gitlab-org/gitlab-ce/issues/24945 is a Platform in GitLab FOSS issue. @mydigitalself : Could you speak to it? It has a 10.1 milestone. That means it is planned for 10.1 release @eliran.mesika .

Regarding gitlab-foss#31847 (moved) and gitlab-foss#34284 (moved), the earliest we would consider these is for 10.2, since 10.1 scope is already established. Perhaps we can try to get at least one of them for 10.2. But I can't say for sure now.