[FR] End of Beta 1.2.0

[x1nf3ctAdusX]

Checks

• I have checked existing OPL feature requests for duplicates and found none

Describe the FR

I'm always frustated when a new feature is added and It doesn't work for me. I always follow, step by step, the tutorials made by Venão, from the Brasilian youtube channel HardLevel, his tutorials are kind the "Official" here because he's the best when talking about the PS2 modding scenario, but it isn't always that everything works for me, so I think these new feature aren't as polished as they sould be, so...

Describe the solution you'd like

As for me, I imagine this beta is taking so long to finish, I think you guys should focus going forward on stabilizing OPL with all major features added so far in Beta 1.2.0, such as the MX4SIO, exfat and the .zso extension suppoprt along with the PS2RD Cheat Engine Integration, Multiple BDM Devices Support, and backgroud Music in the main menu, which are kinda "stable", make a new stable version and jump straight to Beta 1.2.1 or whatever name you guys want name the new beta phase, to keep adding features, over features, what do you all think???

P.S.: I think you developers should make easy text and video based tutorials of every feature added so far and whenever you launch a new feature, so they'll become the official tutorial for the main fork of the OPL, officially made by the developers of the great OPL, what do you all also think???

Describe alternatives you've considered

No response

Additional context

I personally can't see the end of this Beta phase, nor where it started, as so many others, so 100% stabilizing all current features, making a new stable version and jumping straight to next beta phase would be perfect.
Making official tutorials would be the perfect way to tell all OPL intusiasts, such as myself, that you all guys care so much for the project

[rickgaiser]

I totally agree and I think this is what everyone wants.

But...

Each time I suggest to make a release, everyone starts making lists of things that need to be fixed first, like "100% stabilizing all current features". But no developer seems interested or capable at fixing this list. We are currently at exactly 400 open issues (your feature request being the 400th issue). So we're stuck.

As for versioning: https://semver.org/

"you guys should focus" / "I think you developers should"
Keep in mind that we are not a group working together on the same goal. We are all individuals that do in their spare time whatever we like to do. Obviously it's more easy and fun to add new features, then it is to track bugs and fix issues created by others.

[KrahJohlito]

I totally agree and I think this is what everyone wants.

But...

Each time I suggest to make a release, everyone starts making lists of things that need to be fixed first, like "100% stabilizing all current features". But no developer seems interested or capable at fixing this list. We are currently at exactly 400 open issues (your feature request being the 400th issue). So we're stuck.

As for versioning: https://semver.org/

"you guys should focus" / "I think you developers should" Keep in mind that we are not a group working together on the same goal. We are all individuals that do in their spare time whatever we like to do. Obviously it's more easy and fun to add new features, then it is to track bugs and fix issues created by others.

The issue tracker is a big problem atm with many dupe issues, not related, already completed or reports for outdated versions (from many many years ago)… personally I think it would be a good idea to scrub the issue tracker entirely, release a new “stable”, switch to the versioning scheme you’ve linked above and only accept issues that are relevant and for the current release version..

[mystyq]

I can see how once the large HDD support and boot speed improvements get merged, a major release might happen in its current state. Once the news spreads about a new OPL release, it should bring in more users, perhaps some knowledgeable enough to help out with the project