You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Staging does not contain key fixes from master, so whenever I try to test my changes against prod it fails horribly (mostly due nonce change, but that is just a symptom of the problem).
Staging needs to contain all things from master or reliable testing won't be possible.
This also means that whoever will be developing code from staging as per CONTRIB instructions, after their work gets merged into staging and then someone tries to merge it into master they have to resolve all conflicts themselves during release. So testing with staging gets invalidated, as it creates yet another occasion to introduce bugs.
Staging does not contain key fixes from master, so whenever I try to test my changes against prod it fails horribly (mostly due nonce change, but that is just a symptom of the problem).
Staging needs to contain all things from master or reliable testing won't be possible.
This also means that whoever will be developing code from
staging
as per CONTRIB instructions, after their work gets merged into staging and then someone tries to merge it into master they have to resolve all conflicts themselves during release. So testing with staging gets invalidated, as it creates yet another occasion to introduce bugs.Seems like release process described in https://github.com/opentensor/bittensor/blob/master/contrib/DEVELOPMENT_WORKFLOW.md#release-branches was not followed for last couple releases thus creating this problem.
The text was updated successfully, but these errors were encountered: