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

Restructure Upgrading #57

Open
zerocrates opened this issue May 17, 2023 · 2 comments
Open

Restructure Upgrading #57

zerocrates opened this issue May 17, 2023 · 2 comments

Comments

@zerocrates
Copy link
Member

The Upgrading instructions have several caveats throughout that aren't really relevant for the vast majority of users.

We should probably just pull all those notes out into a separate heading, to say OK, if you're using 0.9 (!) then db.ini is here, if before 2.0 "files" is "archive", etc, without cluttering the basic instructions.

@allanaaa
Copy link
Contributor

Sounds good. Also an argument for versioning the docs.

@zerocrates
Copy link
Member Author

The Upgrading page is a bit of an odd duck in that it's always going to have some interest in talking about older versions, even in a hypothetical versioned-docs world.

There's also the reality that the versions that have relevant-for-upgrading differences are all really old: we haven't changed anything in this area for a long time and aren't really likely to do so.

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