If this extension is moved to Gitlab, it would really be ideal if the Github issues and open PRs could be moved there too. If not then I'd say just keep it here.
Is there a detailed revision history somewhere of what changes have been made to this extension? It seems like recent updates may have resulted in compatibility issues. Also, some changes to price sets in core may be related to these issues. I have to say that it seems like CiviCRM could use better change control like is in place for Drupal projects. What would be a proper way to fundraise for someone to put in the needed work to resolve the current issues and help maintain this extension? We would be willing to make a contribution towards this effort.
@lkuttner I think it's best to open a new issue for each of the bugs you encountered. Thank you for the offer of funding! The core team can look at those issues for you and give you an estimate for the cost to fix them.
I'm not quite sure what you mean by "change control". My understanding is that both Drupal and CiviCRM use git for version control and both employ CI infrastructure with php-based unit tests. Also like Drupal, the Civi extension ecosystem is a bit of a Wild West. Code quality and stability can be quite different from one contrib project to the next - some maintainers meticulously write unit tests, upgrade scripts, and release notes; others do not. Some projects have active maintainers, others are minimally maintained or abandoned.
Thanks @colemanw, there are existing posts from myself and others about the current issues, such as this. Some of the issues may be with changes to core, or it may be a combination of changes. I will look into this further and determine if there are problems which should be submitted as separate issues.
Currently, CiviDiscount 3.8.4 is totally unusable on our server with Drupal 7.82 and tested with both CiviCRM 5.33.5 and 5.39. It appears there were significant changes since 3.7. That is the version we are continuing to use with a small modification to resolve a recent new problem with that.
Change control is a formal process where any changes are proposed with an opportunity for the userbase to consider benefits or potential incompatibilities. After responses are reviewed, a dev version is released for testing and feedback. After sufficient testing by others, and after all problems are resolved, then an updated version is released. This helps to reduce the risk of an update breaking an organization's live website.
There was a bit of confusion around who maintains this extension, so I added @mattwire as co-maintainer, while leaving Coleman as unofficial-just-helping-out co-maintainer.