-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Request] TriliumNext #14096
Comments
Should we add TriliumNext as a new package or should we point the existing Trilium package to the new one? |
IMHO I would launch it as a new package. While the database and sync server is fully compatible between Trilium and TriliumNext right now, it could change in the future and there could be breaking changes impossible to revert. Also, if Trilium is in maintenance mode, there could still be security updates. |
Since a few days ago, TriliumNext added some features and bumped database sync version to 33, whereas Trilium uses version 32. This confirms that it should be a separate package, because you can't connect latest TrilliumNext release to old Trilium database anymore. |
Since the original Trilium is now in maintenance mode and the people at TriliumNext are keeping the project alive and adding more features, it would be nice to have it on scoop.
Greetings
The text was updated successfully, but these errors were encountered: