<commit_before>=================================
Wagtailmenus 2.6.0a release notes
=================================

.. contents::
    :local:
    :depth: 1


What's new?
===========

Improved compatibility with alternative template backends
---------------------------------------------------------

Wagtailmenus has been updated to use backend-specific templates for rendering, making it compatible with template backends other than Django's default backend (such as ``jinja2``).

Although the likelihood of this new behavior introducing breaking changes to projects is minute, it is turned **OFF** by default for now, in order to give developers time to make any necessary changes. However, by version 2.8 the updated behaviour will replace the old behaviour completely, becoming non optional.

To start using wagtailmenus with an alternative backend now (or to test your project's compatibility in advance), you can turn the updated behaviour **ON** by adding the following to your project's settings:

.. code:: python

    WAGTAILMENUS_USE_BACKEND_SPECIFIC_TEMPLATES = True

Thank you to <NAME> (hongquan) for contributing this!


New tabbed interface for menu editing
-------------------------------------

In an effort to improve the menu editing UI, Wagtail's ``TabbedInterface`` is now used to split a menu's fields into two tabs for editig: **Content** and **Settings**; with the latter including panels for the ``max_levels`` and ``use_specific`` fields (which were previously tucked away at the bottom of the edit page), and the former for everything else.

Two new attributes, ``content_panels`` and ``settings_panels`` have also been added to ``AbstractMainMenu`` and ``AbstractFlatMenu`` to allow the panels for each tab to be updated independently.

If for any reason you don't wish to use the tabbed interface for editing custom menu models, the ``panels`` attribute is still supported, and will setting that will result in all fields appearing in a single list (as before). However, the ``panels`` attribute currently present on the ``AbstractFlatMenu`` and ``AbstractMainMenu`` models is now deprecated and will be removed in the future releases (see below for more info).<commit_msg>Designate 2.6 as LTS release and announce dropping of Python 2 support in coming releases<commit_after>=================================
Wagtailmenus 2.6.0a release notes
=================================

.. contents::
    :local:
    :depth: 1


.. NOTE ::
    
    Wagtailmenus 2.6 is designated a Long Term Support (LTS) release. Long Term Support releases will continue to receive maintenance updates as necessary to address security and data-loss related issues, up until the next LTS release (for at least 8 months). 

.. NOTE ::

    Wagtailmenus 2.6 will be the last LTS release to support Python 2.


What's new?
===========

Improved compatibility with alternative template backends
---------------------------------------------------------

Wagtailmenus has been updated to use backend-specific templates for rendering, making it compatible with template backends other than Django's default backend (such as ``jinja2``).

Although the likelihood of this new behavior introducing breaking changes to projects is minute, it is turned **OFF** by default for now, in order to give developers time to make any necessary changes. However, by version 2.8 the updated behaviour will replace the old behaviour completely, becoming non optional.

To start using wagtailmenus with an alternative backend now (or to test your project's compatibility in advance), you can turn the updated behaviour **ON** by adding the following to your project's settings:

.. code:: python

    WAGTAILMENUS_USE_BACKEND_SPECIFIC_TEMPLATES = True

Thank you to <NAME> (hongquan) for contributing this!


New tabbed interface for menu editing
-------------------------------------

In an effort to improve the menu editing UI, Wagtail's ``TabbedInterface`` is now used to split a menu's fields into two tabs for editig: **Content** and **Settings**; with the latter including panels for the ``max_levels`` and ``use_specific`` fields (which were previously tucked away at the bottom of the edit page), and the former for everything else.

Two new attributes, ``content_panels`` and ``settings_panels`` have also been added to ``AbstractMainMenu`` and ``AbstractFlatMenu`` to allow the panels for each tab to be updated independently.

If for any reason you don't wish to use the tabbed interface for editing custom menu models, the ``panels`` attribute is still supported, and will setting that will result in all fields appearing in a single list (as before). However, the ``panels`` attribute currently present on the ``AbstractFlatMenu`` and ``AbstractMainMenu`` models is now deprecated and will be removed in the future releases (see below for more info).
{'fraction_non_alphanumeric': 0.1278614147246855, 'fraction_numerical': 0.004743246030109301, 'mean_word_length': 4.041580041580041, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7565445', 'n_tokens_mistral': 1160, 'n_tokens_neox': 1092, 'n_words': 643}