Juniper OSPR wishlist

Working Groups Build-Test-Release
1

Here’s a list of OSPRs that we’d love to get into Juniper. Note that these are not critical issues, but would save OpenCraft from maintaining code drift in our release branch.

These OSPRs fix bugs/warnings:

And these add features:

2

We don’t have a PR for it yet, but there will be an update to the SGA xBlock to fix a python3 bug.

3

@jill can you please add https://github.com/edx/edx-platform/pull/23861 to the list?

4

Sure thing @regis , done.

5

And this one as well please! https://github.com/edx/edx-platform/pull/23862

1 Like
6

It looks like the Python3 upgrade for SGA wasn’t complete or correct. I’m not sure yet how long this may take.

7

@nedbat @regis That’s a topic we didn’t discuss during the last release upgrade meeting - will we be able to include any of these in the Juniper release?

8

@antoviaque goodppoint! I think we must, yes.

9

I merged a few of these, and tagged the rest so they would appear on the new Juniper issues board.

1 Like
10

@jill it’s think we sort these PRs so that we can better see which ones are already merged and who is blocking the merging of the other ones:

Merged.

Merged.

Waiting for review by @mulby.

Waiting for review from @marcotuts.

Merged or rejected, we can close.

Waiting from feedback from @giovannicimolin

Merged.

Waiting for review from @marcotuts.

Merged.

Waiting for @nberdnikov to assign a reviewer.

Waiting for feedback from @fredsmith.

If you have been tagged in this post, it means that your input is expected on a PR that is blocking the Juniper release. If you are not available during the coming days, please assign the task to someone else. Thank you!

2 Likes
11

Thank you for merging so many OSPRs @nedbat! I started pinging you on individual merged PRs to make sure they get included in the Juniper release branch… but then figured that would be noisy and annoying. How would you like us to do this?

12

I’m not sure the best way to raise the visibility of the pull request. We should really be closing down the Juniper release soon. If you mention Juniper in the pull request, I will try to take a look at them.

13

Thank you @nedbat! We’ll do that.

I also saw your message on configuration#5691, that since edX haven’t cut the juniper.master branch yet, anything merged to master prior to that cut will be in Juniper. Good to know!

14

We’ve fixed the python3 bugs in SGA and the new version was merged into master’s requirements on 5/19. So this should not longer be a blocker for Juniper.