Skip to content
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

staging does not contain master changes #1966

Closed
mjurbanski-reef opened this issue Jun 1, 2024 · 0 comments
Closed

staging does not contain master changes #1966

mjurbanski-reef opened this issue Jun 1, 2024 · 0 comments

Comments

@mjurbanski-reef
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants