Roberto,

Mayan 2.0 is a great accomplishment for Mayan EDMS, and you deserve a huge
round of applause for making it happen!

Please do not take my question the wrong way. Since Django 1.7x is no
longer supported and does not receive bug fixes or security fixes, when do
you think Mayan will move to Django 1.8.x? I am sure you know that Django
1.8 is a is a long-term support release and will receive security updates
until April 2018 as described at
https://www.djangoproject.com/download/#supported-versions.

Again, not trying to take anything away from Mayan 2.0. I just see emails
on the Django list that tell developers to stop using Django 1.7 apps. I
was also thinking of your new web site, and I am sure the question will
come up there.

All the best in 2016!

Mark

On Fri, Dec 4, 2015 at 5:57 PM, Roberto Rosario <
[email protected]> wrote:

> I am pleased to announce the immediate availability of Mayan EDMS 2.0.
> This is a stable release and a major version. This is summary of the most
> noteworthy changes:
>
>    - Update the Django version used to 1.7.10. This allows Mayan EDMS to
>    make use of Django's AppConfig and the new native migrations. This change
>    also removes the need for South migrations and support for Python 2.6 and
>    lower.
>    - New Twitter Bootstrap user interface. This new UI allows for much
>    easier customization by support providers or integrators.
>    - Easier 3rd party customization, this is achieved by separating
>    appearance, and authentication into separate apps. Support for
>    unregistering links was added to allow 3rd party apps to modify the
>    navigation without having to modify the code of other apps.
>    - Several custom signals were added to improve the integration of 3rd
>    party apps.
>    - UI simplification: Seldom used link are now hidden from view
>    reducing the visual complexity of the interface.
>    - Improve document preview generation. The entire image generation
>    system was re-factored making it more robust and extensible. It now also
>    allows sharing of the document image cache between nodes of a multi node
>    install of Mayan EDMS.
>    - Smarter document text parsing using a combination of parsing
>    fallback to OCR on a per page basis, this means that text extraction from
>    documents with both text and images is done in the best way possible
>    without sacrificing speed (when no OCR is needed) and quality (when the
>    page only has parseable text).
>    - The access control system (ACL) was re-factored for speed and
>    simplicity. It also now allows a different type of permission inheritance,
>    permission can be granted for a document type and all documents of that
>    type will inherit from it. This new inheritance model makes the use case of
>    having to alter the ACL of individual documents a rare edge case.
>    - Metadata validators were split into validators which block data
>    entry is they raise and error, and parsers which allow invalid data to be
>    entered but parse it and transform it before being stored.
>    - Trash can support was added to reduce the change of accidentally
>    deleted documents.
>    - Retention policies were added to auto trash documents and/or auto
>    delete them too. This is useful if a document contains confidential
>    information and organizational policies or governing laws dictate that is
>    must be destroyed after a specific amount of time.
>    - Sharing of document indexes was added back but implemented as a FUSE
>    filesystem this time. This new mirroring approach allows sharing of indexes
>    even when the filesystem used to store the document is not even local.
>    - Removal of Python's eval from the code. Instance where users are
>    allowed to use the documents properties or make a value template (Metadata
>    type default, metadata lookup, smart links, index template) now use the
>    Django's template language. This eliminates security exploits based on
>    Python's eval abuse.
>    - Improved failure tolerance, Mayan EDMS now detects several critical
>    failures in database access and retry them in a way that greatly reduces
>    the chance of data loss even during conditions where most software would
>    produce a service exception and abort. For more information:
>    
> http://blog.robertorosario.com/testing-django-project-infrastructure-failure-tolerance/
>    - Documents tags now allow any color combination and not just the
>    colors that were included in the past.
>    - Code test improvements was a focus point of this release increasing
>    the total number of test by an order of magnitude, adding the use of tox,
>    adding continuous integration with GitLab CI, CodeCodev integration, adding
>    a custom test runner, and improving the philosophy of test by testing
>    views, models and API separately and checking for both, success and
>    failures of each test's element.
>    - A new simple 'performupgrade' management command was added to reduce
>    the steps required to just one (not counting requirements updates steps).
>    - Automatic debug logging during development and automatic information
>    logging during production, making reporting issues much easier.
>    - This release also includes a Docker image and a Docker Compose file
>    for easier deployments.
>
> For the complete list of changes read the release notes at:
> http://mayan.readthedocs.org/en/latest/releases/2.0.html
> Big thanks to all contributors, testers, translators, mailing members,
> supporters and users.
>
>  - Release Notes: http://mayan.readthedocs.org/en/latest/releases/2.0.html
>  - Downloads: https://pypi.python.org/pypi/mayan-edms/2.0.0
>  - Code: https://github.com/mayan-edms/mayan-edms
>  - Mailing list: https://groups.google.com/forum/#!forum/mayan-edms
>  - Homepage: http://www.mayan-edms.com/
>  - Issues, bugs: https://gitlab.com/mayan-edms/mayan-edms/issues
>
> Social media:
> - Facebook: https://www.facebook.com/MayanEDMS
> - Twitter: https://twitter.com/MayanEDMS
> - Google Plus: https://plus.google.com/108413286958999778262
>
> --
>
> ---
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to