Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the edx GitHub organization from the release process #203

Closed
kdmccormick opened this issue Oct 11, 2022 · 4 comments
Closed

Remove the edx GitHub organization from the release process #203

kdmccormick opened this issue Oct 11, 2022 · 4 comments
Assignees
Labels
enhancement Relates to new features or improvements to existing features

Comments

@kdmccormick
Copy link
Member

kdmccormick commented Oct 11, 2022

Context

Per https://discuss.openedx.org/t/interim-guidance-on-the-openedx-github-organization/8518, the Palm release must only tag repositories in the openedx GitHub organization.

This is related to, but not the same as: #238

Acceptance Criteria

(this might be better split up into subtasks)

Update the comment in openedx.yaml within edx-cookiecutters to explain that, in addition to setting the ref: key, the repo will need to be moved into the openedx organization in order to be released.

Look through our documentation on the wiki; see if there's anything along the lines of "how to get your repository into the release". If there is, update it to include filing a tCRIL request to move the repository into the openedx org.

Generate the list of repos that would be included from the edx org. As of Olive this was:

edx/edx-e2e-tests
edx/enterprise-access
edx/frontend-app-communications
edx/frontend-app-learner-dashboard
edx/frontend-app-ora-grading
edx/testeng-ci

but it would be best to re-generate this list closer to Palm.

Create tCRIL request tickets to move all of those repositories into the openedx organization. Tag the owners/maintainers of the repositories and ask if they have any objections to the move. If they object, we'll need to decide whether:

  • we remove the repo from Palm, or
  • we fork the repository in despite their objection (hopefully this won't need to happen).

Update the release script to only pull from the openedx organization.

@kdmccormick kdmccormick self-assigned this Oct 11, 2022
@kdmccormick kdmccormick changed the title Remove the edx organization from the release process Remove the edx GitHub organization from the release process Oct 11, 2022
@kdmccormick kdmccormick removed their assignment Oct 17, 2022
@arbrandes arbrandes added the enhancement Relates to new features or improvements to existing features label Dec 6, 2022
@feanil
Copy link

feanil commented Dec 20, 2022

openedx/axim-engineering#591 takes care all the repos except for edx/edx-e2e-tests which has a PR against it to remove it from the release process.

feanil pushed a commit to openedx/repo-tools that referenced this issue Jan 3, 2023
Relates to openedx/wg-build-test-release#203

BREAKING CHANGE: We will no longer look in the `edx` org for repos to
tag during the release process.
feanil pushed a commit to openedx/edx-cookiecutters that referenced this issue Jan 3, 2023
Make it clear that the release option won't do anything unless the
repository is in the `openedx` organization in github.

Relates to: openedx/wg-build-test-release#203
feanil pushed a commit to openedx/repo-tools that referenced this issue Jan 3, 2023
Relates to openedx/wg-build-test-release#203

BREAKING CHANGE: We will no longer look in the `edx` org for repos to
tag during the release process.
@feanil
Copy link

feanil commented Jan 3, 2023

I think once the following PRs merge, we can mark this as complete:

@feanil
Copy link

feanil commented Jan 4, 2023

Both PRs have merged so this is now all set.

@feanil feanil closed this as completed Jan 4, 2023
@kdmccormick
Copy link
Member Author

Thanks Feanil!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Relates to new features or improvements to existing features
Projects
Development

No branches or pull requests

3 participants