Following on from the discussion on GitHub issue #1928 <https://github.com/stephenmcd/mezzanine/issues/1928>
Throughout 2019 there has been 1 commit to the master Github repo, we haven't had a full release since August 2018 and there are a number outstanding changes that are waiting to go into a new release. We still don't have Django 2 support despite it being released in December 2018 and Django 3 is now out and available for development. I use Mezzanine a lot in my day to day projects but I don't feel like I personally have the skill to take it forward and make it fully compatible with the changes to Django and jQuery that are required. Basically, I feel that this project needs a bit of help to keep it relevant. Thankfully there are maintainer communities in Jazzband <https://jazzband.co/>and Code Shelter <https://www.codeshelter.co/> that may be able to help us. I feel that handing the project over to them should at least ensure that active Mezzanine projects are not left exposed when 1.11 is deprecated in April 2020. Also - just to note - this is in no way mean to denigrate the hard work that Stephen and others have done over the years with this project, it speaks volumes about the quality of the codebase that Mezzanine is still my Django CMS of choice after all this time. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mezzanine-users/476a90bc-1e21-4cfe-8039-b72a6e1748eb%40googlegroups.com.
