There are some users reaching out that are trying to use our main branch but this is in active development. I would like to apply a new branch structure to better fit with professional companies.
This will include the following branches:
Main Branch: The currently released PyPI code
Test Branch: A stable version of the next PyPI release meant for testing to identify and fix bugs.
Dev Branch: An unstable version of the next PyPI release meant to hold our next fixes and features.
Fix Branches: Specific fixes being worked on, which will eventually be merged to the Dev Branch.
Feature Branches: Specific features being worked on, which will eventually be merged to the Dev Branch.
The idea is we work on fix and feature branches more independently and when these are done, we merge to the Dev Branch, which will accumulate all changes for the next release. Once all targeted bugs have been fixed and features implemented, and the Dev branch is fully merged without conflicts and runs on the surface, the Dev Branch gets pushed to the Test Branch, where the package is fully tested.
There are some users reaching out that are trying to use our main branch but this is in active development. I would like to apply a new branch structure to better fit with professional companies.
This will include the following branches: Main Branch: The currently released PyPI code Test Branch: A stable version of the next PyPI release meant for testing to identify and fix bugs. Dev Branch: An unstable version of the next PyPI release meant to hold our next fixes and features. Fix Branches: Specific fixes being worked on, which will eventually be merged to the Dev Branch. Feature Branches: Specific features being worked on, which will eventually be merged to the Dev Branch.
The idea is we work on fix and feature branches more independently and when these are done, we merge to the Dev Branch, which will accumulate all changes for the next release. Once all targeted bugs have been fixed and features implemented, and the Dev branch is fully merged without conflicts and runs on the surface, the Dev Branch gets pushed to the Test Branch, where the package is fully tested.