LAME pre-dates the times when it became usual that OSS projects have a CI/CT process. Additionally all those people which worked on LAME are inactive.
So:
Have a look at what kind of optional stuff the Windows build infrastructure provides right now, compile test them (except the gtk analyzer, this is know to have bitrotted), and do a test conversation of some audio file.
Once all is ok, submit a diff (against the head of SVN, not against the last released code) here as a patch. No promises on when it would be integrated into SVN, no promises about a release (when I have the time, I don't think about LAME, and when I think about LAME, I don't have the time).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
LAME pre-dates the times when it became usual that OSS projects have a CI/CT process. Additionally all those people which worked on LAME are inactive.
So:
Have a look at what kind of optional stuff the Windows build infrastructure provides right now, compile test them (except the gtk analyzer, this is know to have bitrotted), and do a test conversation of some audio file.
Once all is ok, submit a diff (against the head of SVN, not against the last released code) here as a patch. No promises on when it would be integrated into SVN, no promises about a release (when I have the time, I don't think about LAME, and when I think about LAME, I don't have the time).