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

Submit PR back upstream on completion #12

Open
jwflory opened this issue Dec 9, 2016 · 0 comments
Open

Submit PR back upstream on completion #12

jwflory opened this issue Dec 9, 2016 · 0 comments
Assignees

Comments

@jwflory
Copy link

jwflory commented Dec 9, 2016

Related to FOSSRIT/PyCut#37.

Summary

Once the project is complete, a pull request of your work back to the upstream repository should be made in the spirit of collaboration and growth of PyCut.

Analysis

This issue should be the last one closed for the semester. Once the project is at a "final" state, a team member can initiate a single, large pull request of the repository to the upstream. Since instead of smaller, incremental PRs we are doing one big one, it would be courtesy for the upstream maintainer to see what changes you are adding in your pull request and how rigorously they have been tested. A bulletpoint changelog of additions, modifications, and removals would expedite the process for the PR to be merged back into the upstream version and to cut a new release.

As noted, it's also a good idea to make notes of (1) what the proposed changes were tested on (e.g. what XO model), and (2) any other notes about the changes that should be made known.

Implementation

  1. At end of project, compile a list of additions, modifications, and removals to PyCut since you all started working on it
  2. Format the changes into a bulletpoint changelog
  3. One team member initiates the PR back to the upstream FOSSRIT/PyCut repository
  4. An upstream maintainer reviews changes, provides feedback as necessary
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants