#8699 Module EOL & Removal from F31 before GA [mysql, mariadb]
Closed: Fixed by mohanboddu. Opened by mschorm.

Hello,
I'd like to stop building a number of module streams for Fedora; and also I want some to be removed from Fedora 31 before it's GA.

  • Name of the modules?
    mysql
    mariadb

  • Stream name(s) and the new EOL date?
    mysql
    -- 5.6: EOL ASAP
    -- 5.7: F31 EOL date
    -- 8.0: Extend as much as possible
    mariadb
    -- 10.1: EOL ASAP
    -- 10.2: EOL ASAP
    -- 10.3: Extend as much as possible
    -- 10.4: Extend as much as possible

  • Any extra information?
    The MySQL 5.6 Module wasn't updated for a year and I have no capacity nor plan to do so. Thus there are also security vulnerabilities without any fix.
    It was automatically built for F31, but I rather want to see that stream dead, so I can focus on the latest 8.0 stream. The 8.0 stream will not EOL anytime soon so I would like to postpone the proposed EOL date.
    The 5.7 stream also wasn't update for a very long time. It was intended as an alternative for a users who needed more time to upgrade from MySQL 5.7 to 8.0. I'd like to align it's EOL with the F31 EOL.
    The MariaDB 10.1 is a simmilar story to MySQL 5.6. If still alive, please terminate it too, ASAP. Don't allow it to get into F31.
    MariaDB 10.2 should be dead, I just want to make sure.
    MariaDB 10.3 & 10:4 are simmilar to MySQL 8 - will not EOL anytime soon.

I'm a maintainer of both MariaDB & MySQL. They have a very common ground so that's why I use one ticket for both of them.


Done.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata