-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Divide et impera #190
Divide et impera #190
Conversation
…o changes on the module internal mechanism, only code movement from a file to another
it's a big PR, not sure if I have the time to review it soon :( |
Do not worry, i have no rush or bad feelings about it. Take all the time you need. |
I think we should merge this asap, maybe we can "versioning" this module and add to the readme the commit/link to the version before this as a stable version, and this will stay in "beta" until we ensured that everything is working unless there's someone that wants to test it extensively right now, but I'm afraid that the more time we wait the worse it will be to resolve the conflicts with other incoming PRs |
@kewinrausch you could add a note in the README.md about this PR, saying that from this PR the module could be "unstable" and we'll merge the PR ;-) I appreciate the big effort here, this note it's only to keep track of this |
I did as you requested. Wouldn't it be better to create also a tag or a branch pointing to the stable version right now? Once enough time has passed and enough test have been performed the branch can be removed to maintain only the master one. |
done ✅ |
Changes Proposed:
Issues Addressed:
SOURCE:
Tests Performed:
How to Test the Changes:
Take you time to confirm that the module work as intended.
I'm personally performing additional tests to be sure the balancing is not affected. I expect no problem since i just moved code around files and did not touch the code inside the classes and procedures.