35.x epic

[jamesmontalvo3]

This issue is to track issues related to having a stable 34.x 35.x release. The 34.x 35.x branch is out there, but it has issues. Another consideration is that 34.x may not be maintained as a major version of Meza, and we may move straight to 35.x if that seems feasible.

Required fixes

• Ensure always the same version of Elasticsearch is used (6.x)
• Make 34.x pass tests
• Error deploying v34 #1251 Error deploying v34 - I believe this is resolved in the latest 34.x branch but would like confirmation from @revansx and/or @freephile
• Make all extensions which work in 31.x work with 34.x
  • Uncomment any commented-out extensions
  • Test those marked with comment "verify 34.x functionality" in MezaCoreExtensions.yml
    • ParserFunctionHelper
    • MezaExt
    • TalkRight
    • CopyWatchers
    • Wiretap
    • ImagesLoaded
    • MasonryMainPage
    • WatchAnalytics
    • SemanticMeetingMinutes
    • HeaderFooter
  • Test all others (the extensions above are higher risk since EnterpriseMediaWiki "maintains" them)
• Which extensions should be installed by default by Meza? #1264 Determine which extensions should be installed by default
  • Provide upgrade path that allows users to easily convert old MezaCoreExtensions.yml extensions to MezaLocalExtensions.yml extensions.
• Either (a) make it work on Debian/Ubuntu and provide comprehensive tests or (b) remove Debian/Ubuntu support
  • 35.x - Decide whether to support anything but CentOS #1300 Decide whether to support anything but CentOS
  • PIP and Easy install not found on Debian #1266 PIP and Easy install not found on Debian
  • Issues getting meza to run on debian (raspbian lite) #1160 Issues getting meza to run on debian (raspbian lite)
• Determine whether to support install locations other than /opt/meza (which is poorly supported now) 35.x - Decide whether to support alternate install locations (not /opt/meza) or encourage symlinking #1302

Desired additions

• Upgrade MariaDB to 10.6 or higher #1250 Upgrade MariaDB to 10.4 or higher
• Ideally support PHP 7.4. This is so it doesn't go EOL before the next MW LTS (MW 1.39 released in spring 2022, PHP 7.4 EOL late 2022). This is not a show-stopper. If there are issues with 7.4 we can do 7.3 or 7.2 if required. PHP 7.4 is version on 35.x branch
• Determine upgrade path for PHP. 7.4 may be last version in IUS repo, since IUS may not be getting as much support as it once did
• External images don't load in VE without fix / Properly deal with "image list" functionality #149 External images don't load in VE without fix
  • See if changes have been implemented in MW core, or will this go away when Parsoid becomes part of core in ~1.35?

Is there more? Please comment if there are more items that should be added to this list. Or let me know if anything on the list is complete.

[jamesmontalvo3]

34.x just passed tests after working around issues with Elasticsearch, SMW, and Multi-Content Revisions.

[jamesmontalvo3]

Added requirement: "Either (a) make it work on Debian/Ubuntu and provide comprehensive tests or (b) remove Debian/Ubuntu support"

[jamesmontalvo3]

Added decision required: #1302

[alberttwong]

#1310