I've started merging the changes from Mayan EDMS NG. After getting all code revisions for version 2.8 I looked at the changes in version 3.0 and there we some good bug fixes and should be included. After adding the 3.0 bug fixes there was not real reason not to continue the merge of the remaining Mayan EDMS NG version 3.0 features.
As of today practically all Mayan EDMS NG changes and additions have been included into what will be the next Mayan EDMS. The next release version of Mayan EDMS will be version 3.0. The version number will go from 2.7.3 to 3.0 skipping 2.8 and 2.9. The reasons for this jump in versions are: - All changes from Mayan EDMS NG 2.8 and 3.0 were merged. Makes better sense to keep version numbers in sync with the most prominent fork. - The authors of Mayan EDMS NG have no desire to maintain a free open source fork over the long run. And explained their work was meant to be temporary help to keep the project's momentum during my absence. - API incompatible changes. The URLs for the API changed. This alone prompts a major number increment according to the semantic versioning best practices. The inclusion of a new Django version (1.11). Aside from this everything else is perfectly compatible. Database migrations are provided to allow upgrade of existing installation like any other previous release. - My way of saying thank you for sticking around and supporting the project. It has been several months since the last release (2.7.3) so what better surprise than to launch a big release with lot of new features. These are the only release blockers: - Update Chart.js - Update toastr.js - Add support for downloading the event log - Check and fix high priority issues in GitLab - Check and tix milestone 3 issues in GitLab - Add Flake8 step to release checklist. - Unify use os.unlink - Audit the os.unlink uses in the code. Check that they are local and do not require Django storage. After the release blockers there are some issues I would like to close if they don't prove too difficult and don't delay thinks too much. - More compression types support (tar). Finish Git feature branch. - Image overlay or watermark for when there is no print permission assigned. HIPAA requirement. - Skip bad document signatures during perform upgrade - Move the MetadataLookupIntegrationTestCase from user_management to metadata. - Reduce document paging size. Or add separate paging sizes. - New installer to create separate sites (no settings.local.py buried) (https://gitlab.com/mayan-edms/mayan-edms/issues/134). Might help with the Docker named volume issue. Work is being done in the versions/next branch: https://gitlab.com/mayan-edms/mayan-edms/tree/versions/next Release notes for what has been done already: https://gitlab.com/mayan-edms/mayan-edms/blob/versions/next/docs/releases/3.0.rst -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
