[Proposal] Legacy code release for backward compatability

[ppasupat]

Proposal

Create a release containing the legacy code (before migrating to Farama).

Motivation

A few projects depend on the old code structure. Examples include:

• Workflow-Guided Exploration
• DOM-Q-NET: Grounded RL on Structured Language
• Environment Generation for Zero-Shot Compositional Reinforcement Learning

To prevent breaking such codebases, it would be nice to create a release containing the legacy MiniWoB++ code.

Pitch

Create a release at commit 833a477a8fbfbd2497e95fee019f76df2b9bd75e, which is right before the migration.

Alternatives

The release should have minimal effects on the current code development.

Checklist

• [x] I have checked that there is no similar issue in the repo (required)

[pseudo-rnd-thoughts]

@jkterry1 Personally I have no issue with this. We can make a v0 release with the legacy code with v1 being the new version

[jkterry1]

Ya that's fine for me

[pseudo-rnd-thoughts]

@ppasupat How would you like to make this legacy release? Im guessing we want a pypi and github release

[ppasupat]

A GitHub release should be sufficient I think. PyPi would be a hassle since the code was not packaged that well, and for reproducibility, I don't want to modify the code too much.

[jkterry1]

Works for me

[ppasupat]

Thank you. Following up on this, I think my GitHub role does not allow me to create a release candidate. Could someone help create the release?

[pseudo-rnd-thoughts]

@ppasupat I have given you permissions to merge PRs etc as you are the main contributor. I think this should give you permissions to create releases just could you run the release notes pass jordan or myself as farama is trying to follow a standard operating procedure. If you don't have a copy of the SOP then just message or ask on Monday

[ppasupat]

The release is now live at https://github.com/Farama-Foundation/miniwob-plusplus/releases/tag/v0.1.