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

The big documentation and development upgrade #1278

Closed
wants to merge 187 commits into from

Conversation

daquinteroflex
Copy link
Collaborator

@daquinteroflex daquinteroflex commented Dec 1, 2023

This is the one we will merge whenever we want to. I am only perfecting things at this point.

Supersedes all others as they are so coupled changes and are hard to break down into smaller bits eg. #1238

First stage implementation of #1148

Could I propose maybe we do this merge independently of 2.6 but before 2.6? Or the documentation upgrade becomes 2.6 and the further upgrades become 2.7?

I just realised I should open this only when pre/2.6 branch is open and maybe only when 2.5 is fully done? Seems like an easy base change whenever we decide.

daquintero and others added 30 commits October 30, 2023 11:51
@daquinteroflex daquinteroflex changed the base branch from develop to pre/2.6 December 14, 2023 12:06
@daquinteroflex daquinteroflex self-assigned this Dec 14, 2023
@daquinteroflex
Copy link
Collaborator Author

Because rebasing was very painful upgrading from here #1319

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

Successfully merging this pull request may close these issues.

3 participants