QA: Separate tests for creating groups and projects

The discussion from !21302 (merged) should be addressed. It was about why a factory wasn't used to create a project. The problem was that with the changes the factory would create a group via the API, so there would be no test of creating a group via the UI.

There are at least two options:

1. Make it possible to fabricate all dependencies via the UI, if desired
2. Separate the UI tests for creating a group and creating a project

I'm in favor of option 2 because if would be good to have separate tests of those features. The current test of creating a project will fail if there's a problem creating a group, which isn't ideal.

mentioned in issue #52019 (closed)

added priority1 label

I also think that option 2 is more ideal because it makes the intention very clear.

added [deprecated] Accepting merge requests label

changed milestone to %12.2

mentioned in issue #63065 (closed)

Milestone %11.11 has expired, this will be rescheduled to the next milestone in active development %12.1. If you think this is incorrect, please feel free to update the milestone to a more appropriate one.

We're also adding missed:11.11

changed milestone to %12.1

added missed:11.11 label

mentioned in issue #65094 (closed)

changed milestone to %12.2

added missed:12.1 label

mentioned in issue #66572 (closed)

mentioned in issue #66594 (closed)

mentioned in issue #66618 (closed)

changed milestone to %12.3

added missed:12.2 label

removed priority1 label

@mlapierre @at.ramya this seems to have missed multiple releases, changing to %Backlog for now. Please feel free to correct me.

changed milestone to %Backlog

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue