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

3.2 Release Tracking #10726

Closed
goanpeca opened this issue Jul 28, 2021 · 21 comments
Closed

3.2 Release Tracking #10726

goanpeca opened this issue Jul 28, 2021 · 21 comments
Assignees
Labels
bug status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Milestone

Comments

@goanpeca
Copy link
Member

goanpeca commented Jul 28, 2021

This issue will gather all issues we will be working on for the 3.2 release.

The list will be updated with issues and PRs that will be included.

This release will have a span of ~2 months so he initial 3.2rc will be planned for the end of September.

Update: the current plan is to have 3.2rc on 5 Oct and a final release on 12 Oct.

Update: the RC went out on 7 October and the plan is for a final release on 14 October.

Issues

Work

@goanpeca goanpeca added the bug label Jul 28, 2021
@goanpeca goanpeca self-assigned this Jul 28, 2021
@goanpeca goanpeca added this to the 3.2.x milestone Jul 28, 2021
@krassowski
Copy link
Member

@goanpeca goanpeca pinned this issue Jul 29, 2021
@joelostblom
Copy link
Contributor

@goanpeca
Copy link
Member Author

goanpeca commented Jul 30, 2021

Hi @joelostblom thanks for chiming in.

That is rather a large endeavor that has stalled, so unless someone champions it full time, I do not think it will make it :-| .

@mlucool
Copy link
Contributor

mlucool commented Aug 3, 2021

Can we add fixes to the document undo/redo #10694 (or maybe this should be 3.1.x)?

@krassowski
Copy link
Member

The PR fixing #10694 is already tagged to 3.1.x (assuming we go with this fix). I would also champion for a fix to #10732 to go into 3.1.x.

@mlucool
Copy link
Contributor

mlucool commented Aug 3, 2021

I only see a PR for undo/redo of outputs. Is there another PR for "allowing users to disable the document-wide history tracking when not in RTC mode"?

I agree that #10732 should also go into 3.1.x.

@goanpeca
Copy link
Member Author

goanpeca commented Aug 9, 2021

I only see a PR for undo/redo of outputs. Is there another PR for "allowing users to disable the document-wide history tracking when not in RTC mode"?

I am not sure we are tracking that as a separate issue. @krassowski do we have such issue?

@krassowski
Copy link
Member

We didn't but now we do: #10791.

@echarles
Copy link
Member

We will need also #10714 in 3.2

@krassowski
Copy link
Member

Did your #10793 fix that? If yes, I would say we should backport to 3.1.

@echarles
Copy link
Member

Did your #10793 fix that? If yes, I would say we should backport to 3.1.

Yes, #10793 is a fix for #10714 in master and also ported and merged in 3.1.x with #10797

@krassowski
Copy link
Member

Thanks! I closed that issue for now to make it clear. I think that 3.2 will just branch off 3.1 so we should not worry about picking up individual PRs that were already backported, but a confirmation from @goanpeca would help here.

@blink1073
Copy link
Member

I updated the top level comment and milestone to reflect the new timeline discussed in today's dev meeting.

@blink1073
Copy link
Member

blink1073 commented Sep 30, 2021

@echarles
Copy link
Member

echarles commented Sep 30, 2021

Enable document wide history tracking #10949

#10949 can be removed from 3.2 as it depends on #11035

@blink1073
Copy link
Member

Thanks @echarles, I meant to put #10769, updated.

@blink1073
Copy link
Member

blink1073 commented Oct 5, 2021

We had some issues related to webpack in #11218 and #11234 that slowed us down today, I'll make the RC tomorrow.

@blink1073
Copy link
Member

Pushing the RC to tomorrow since #11249 will be needed to address upstream changes in openssl

@blink1073
Copy link
Member

RC is out! https://github.com/jupyterlab/jupyterlab/releases/tag/v3.2.0rc0

@blink1073
Copy link
Member

@blink1073 blink1073 unpinned this issue Oct 15, 2021
@github-actions github-actions bot added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Apr 13, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

No branches or pull requests

6 participants