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

Chore/next to develop #4666

Merged
merged 37 commits into from
Apr 15, 2024
Merged

Chore/next to develop #4666

merged 37 commits into from
Apr 15, 2024

Conversation

obycode
Copy link
Contributor

@obycode obycode commented Apr 9, 2024

Merge next into develop to get the latest signer fixes. There should be no consensus breaking changes in this changeset.

jferrant and others added 30 commits March 25, 2024 19:05
Signed-off-by: Jacinta Ferrant <[email protected]>
…user sets max_tx_fee_ustx in the config

Signed-off-by: Jacinta Ferrant <[email protected]>
…into bugfix/enable-dkg-in-current-reward-cycle
…into bugfix/enable-dkg-in-current-reward-cycle
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
…-inc-nonce

Consider nonce when checking for existing vote transactions in stacke…
…into bugfix/enable-dkg-in-current-reward-cycle
…rent-reward-cycle

Do not attempt to treat miner as a coordinator when updating DKG
…le-length-bug

Reward cycle length was being incorrectly stored as reward phase length
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
jferrant and others added 6 commits April 5, 2024 01:28
@obycode obycode requested review from jferrant and kantai April 9, 2024 18:05
@wileyj
Copy link
Contributor

wileyj commented Apr 9, 2024

@obycode is this required for rc2?

@jferrant
Copy link
Collaborator

jferrant commented Apr 9, 2024

@obycode is this required for rc2?

Should not be. This is to port signer changes out of next since signer changes are not consensus breaking and subsequent signer dev should be done from develop. See https://nakamotoslack.slack.com/archives/C067BHSN1SL/p1712679342282899

@wileyj
Copy link
Contributor

wileyj commented Apr 9, 2024

@obycode is this required for rc2?

Should not be. This is to port signer changes out of next since signer changes are not consensus breaking and subsequent signer dev should be done from develop. See https://nakamotoslack.slack.com/archives/C067BHSN1SL/p1712679342282899

ok - let's hold off on merging this then until rc2 is tagged

@hstove
Copy link
Contributor

hstove commented Apr 9, 2024

is this required for RC2?

should not be

ok - let's hold off on merging this then until rc2 is tagged

I understand the reasoning, but unless we have a different release system for the signer, we still really want these changes included when people update or set up their infra. Otherwise, we're just punting these important changes for some later release.

@obycode
Copy link
Contributor Author

obycode commented Apr 12, 2024

ok - let's hold off on merging this then until rc2 is tagged

Since we're releasing from the release/... branch now, I think we're clear to merge this. Please confirm @wileyj.

@obycode obycode requested a review from wileyj April 12, 2024 15:29
@obycode
Copy link
Contributor Author

obycode commented Apr 15, 2024

I just updated this PR with the latest next and develop. Let's get it merged today.

@obycode
Copy link
Contributor Author

obycode commented Apr 15, 2024

Note, there were no conflicts, so this should be a simple review.

@obycode obycode requested a review from a team April 15, 2024 16:47
@obycode obycode merged commit 799c321 into develop Apr 15, 2024
1 of 2 checks passed
@obycode obycode deleted the chore/next-to-develop branch April 15, 2024 17:20
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

Successfully merging this pull request may close these issues.

5 participants