Page History

...

To quickly find PRs assigned to you for review, visit https://github.com/pulls/review-requested  (This is also available in the GitHub header under "Pull Requests → Review Requests")

Try "Pull Request Trading" for a quicker review

Do you have a PR stuck in "under review" that you really want to see move forward?  Or maybe it's someone else's PR but you want to get it more attention?

Use "Pull Request Trading" to get immediate attention.

...

• Please make sure the developer is at a different institution from your own. 

...

• PRs you review or test can be any PR on one of our boards (7.6.1 Board or 8.0 Board), provided they are similar-size to your PR.
• PRs you review or test must be from a developer at a different institution from your own.
• You must submit useful feedback on the PR you've reviewed/tested (via a comment on the PR or similar).  It can be positive or negative feedback (So, if you test it and it doesn't work for you, that still counts).

...

Goals for 8.0

This were decided by Steering in their meeting on June 28, 2023.

...

• Bug/security fixes only.  Release will occur when sufficient fixes have been made to warrant a release.
• Fixes should have two Pull Requests (exceptions may be made for very small fixes)
  1. A PR against the "dspace-7_x" maintenance branch to apply to the next 7.6.x release.
  2. A PR against the "main" branch to fix this same bug for the 8.0 release.
  3. (NOTE: Once one PR is reviewed & approved, the other will be merged at the same time.)

Try "Pull Request Trading" for a quicker review

Do you have a PR stuck in "under review" that you really want to see move forward?  Or maybe it's someone else's PR but you want to get it more attention?

See Trading reviews on Pull Requests for how to get immediate attention to that PR!

Notes