-
Notifications
You must be signed in to change notification settings - Fork 0
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
Decouple the ecommerce repo #96
Comments
@pshiu Let me know how we can work together on this. |
Thanks, @nedbat. I think the plan is to use the |
Sounds like the plan is a sprint or two to get this done. |
As of today, there's a 2u/main branch, but 2U engineers are still committing to master:
|
@wdrussell2015 Can you update us on the status of this? The |
A new Jira issue (private link): https://2u-internal.atlassian.net/browse/REV-3528 |
Latest thinking: this will happen in October after the Django 4.2 upgrade. |
4.2 hasn't landed yet for the ecommerce application. We are blocked not by the process, but by capacity to make this change. Should ecommerce worker also follow the branching strategy we are proposing here? |
@e0d yes, I think so, ecommerce-worker should also follow this pattern. To unblock the django42 upgrade for ecommerce for the community, we are going to begin this change now/soon. I am planning to send out some communications about this today in anticipation of this change coming |
The ecommerce repo has a number of open pull requests that we aren't interested to review, and don't want to risk merging. Can we separate our deployment from the main branch, and let the community move forward?
2u/release
branch instead of master?The text was updated successfully, but these errors were encountered: