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

v0.37 release plan #9091

Closed
32 of 39 tasks
thanethomson opened this issue Jul 25, 2022 · 11 comments
Closed
32 of 39 tasks

v0.37 release plan #9091

thanethomson opened this issue Jul 25, 2022 · 11 comments
Assignees
Labels
release-plan A high-level tracking issue for a specific major release stale for use by stalebot

Comments

@thanethomson
Copy link
Contributor

thanethomson commented Jul 25, 2022

This issue currently targets the v0.37 release.

In order to ship #9053, we need to do the following:

Things that still need to be done before we "feature-freeze" v0.37 and cut the v0.37.x branch:

@thanethomson thanethomson added the T:tracking Tracking issue for other issues label Jul 25, 2022
@thanethomson thanethomson self-assigned this Jul 25, 2022
@thanethomson thanethomson changed the title WIP: ABCI++ Prepare/Process Proposal Release Plan ABCI++ Prepare/Process Proposal Release Plan Jul 25, 2022
@cmwaters cmwaters pinned this issue Jul 26, 2022
@tychoish
Copy link
Contributor

I think the crypto changes are potentially pretty isolated (small), offer some amount of ease, and wouldn't be disruptive to the codebase. (#6120, #5632, #6526)

I think the blockchain/blocksync changes are good, and not very risky, (e.g. removing all of the versions of blocksync that don't work, and have as far as I know never worked, which is to say v1 and v2, and renaming it blocksync rather than blockchain in the code.) At the same time, I'm not sure that people run into this problem in practice (and it's easily recoverable when they do,) so they seem like good things to cut scope on. (#6755, #5728)

The reset are a bit more delicate and have less clear answers, but I've attempted to annotate:

@thanethomson thanethomson added priority A high-priority, high-level item to be shown on the priorities project board and removed T:tracking Tracking issue for other issues labels Jul 27, 2022
@tac0turtle
Copy link
Contributor

Theses are some that I saw quickly but I bet there are other low lift things in the changelog that could be upstreamed to main

@cmwaters
Copy link
Contributor

cmwaters commented Aug 1, 2022

Other than the ones already mentioned, I think the following should be considered streaming in the near term:

The rollback command (#7033) has already been backported to v0.34

I think it would be also nice to add the confix tool that Michael wrote

@williambanfield
Copy link
Contributor

@marbar3778 I'm confused by #5728, I thought v1 ended up being the only reactor, v2, and that that v2 should be targeted for removal.

@tac0turtle
Copy link
Contributor

sorry meant the removal of v1 and v2. grabbed that pr as an example

samricotta added a commit that referenced this issue Aug 16, 2022
* Remove set option for abci
@hdevalence
Copy link

Tendermint 0.35 deduplicated some proto definitions between abci and types, notably the ConsensusParams and the BlockParams. Not including this deduplication in 0.37 will make modeling domain types more difficult.

@hdevalence
Copy link

hdevalence commented Aug 17, 2022

At some point between Tendermint 0.34 and 0.35, the SetOption ABCI request was dropped. I believe it was unused; it's not documented anywhere.

@cmwaters
Copy link
Contributor

At some point between Tendermint 0.34 and 0.35, the SetOption ABCI request was dropped. I believe it was unused; it's not documented anywhere.

v0.37 also drops SetOption - yes it's unused.

@cmwaters
Copy link
Contributor

As to the deduplication of some proto definitions we can and should do that. I have opened a PR here: #9287

@thanethomson thanethomson added release-plan A high-level tracking issue for a specific major release and removed priority A high-priority, high-level item to be shown on the priorities project board labels Dec 22, 2022
@github-actions github-actions bot added the stale for use by stalebot label Mar 25, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 29, 2023
@ashishkhuraishy
Copy link

will the documentation updates also cover fixes to update broken links from the tendermint website?
eg: this is the link which is currently there on Get Started button which redirects to a 404

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-plan A high-level tracking issue for a specific major release stale for use by stalebot
Projects
Status: Done/Merged
Development

No branches or pull requests

7 participants