Topic on Talk:Meza/Flow

With MW 1.31 going end-of-life later this year (Sept 2021), what answer should enterprise users of Meza give to their management when asked if there are any significant software updates to be planned for later this year. Should Meza owners be planning to continue running Meza 31.x in 2022? .. indefinitely? ..or should we be preparing for an upgrade later this year?

I have a development server that is ready to start testing a 35.x deployment, but I am not aware of any specific branch of Meza that has been advertised as ready for user testing and feedback of a MW 1.35 version of Meza.

What is the status of the 35.x branch of Meza?

• Is it scheduled to become the next 'master' branch?
• Should Meza users be testing the 35.x branch and providing feedback? .. or is it not ready ready for user testing and feedback?

Thank you!

/Rich

I began 35.x work earlier this year, but other priorities have made it impossible to complete the work. It'll get done, but unfortunately without assistance or incentive I can't give a schedule.

That is totally understandable. Thanks for responding. We'd like to help (GRC-ATF). We'd like to fork whatever you say is the most current 35.x development and see if we can get some pull-requests your way. All we need to know is what branch you consider to the the right branch to fork. Please let us know. Thanks!

2021-08-28 UPDATE - I just ran a full deploy of the Meza 35.x branch from scratch on a new Centos7 VM in VBox. Except for the last task to verify Python3 in /src/roles/mediawiki/taksk/main.yml the entire install and deploy went without a hitch and I am now testing extensions in 35.x. I will fork this branch in github and try to contribute to it's development. Thanks for getting us this far!