Walletwasabi: v1.1.12 Release procedure plan
v1.1.12 Release procedure plan
- [x] Get things done v1.1.12 Project board.
- [x] Get things done: Hard Fork API v4 Project board.
- [x] Deploy v1.1.12 RC1.
- [x] Create Test Vectors.
- [x] Create Relase notes.
- [x] Start Contribution Game for Review of v1.1.12.
- [x] Final release.
- [x] Check the other Linux download link! https://github.com/zkSNACKs/WalletWasabi/pull/3784
- [x] Resolution of the game.
- [x] Write a summarization article about the release.
molnard
All 8 comments
@molnard Could you always release with the latest .NET Core and an up to date WSL to make sure we don't ruin the deterministic build process?
nopara73
on 20 Jun 2020
@molnard Could you always release with the latest .NET Core and an up to date WSL to make sure we don't ruin the deterministic build process?
Yes, I am doing that already according to https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/ClientDeployment.md#3-packaging
Did I miss something?
molnard
on 22 Jun 2020
Shouldn't we add testing the deterministic builds to the release procedure?
nopara73
on 23 Jun 2020
Get things done: Hard Fork API v4 Project board.
@molnard You didn't forget about this right?
yahiheb
on 13 Jul 2020
@molnard Could you always release with the latest .NET Core and an up to date WSL to make sure we don't ruin the deterministic build process?
I used .NET 3.1.301 x64 and indicated that in the release notes.
molnard
on 14 Jul 2020
Get things done: Hard Fork API v4 Project board.
@molnard You didn't forget about this right?
- Notify institutional users - this will happen after the release.
- Remove unused GET status messages eg. readcount - I am not sure about this @lontivero @nopara73 what do you think?
UPDATE we are not removing it now it will be done with Wabi-Sabi - Remove backward compatibility checks - after the v4 deployed to the main net backend
- Terms and conditions - done
molnard
on 14 Jul 2020
After the release, we should write an article on the blog that summarizes the changelog even for those who are not technical, talk about the contribution game, etc.
We should do this for every release, like btcpay blog. I find it very useful because it summarizes the changes that have taken place in the last months in a few lines.
RiccardoMasutti
on 14 Jul 2020
One more thing remained, the resolution of the game.
https://github.com/zkSNACKs/WalletWasabi/issues/3782#issuecomment-669486876
molnard
on 6 Aug 2020
Related issues
yahiheb
路
3Comments
2pac1
路
3Comments
molnard
路
3Comments
MaxHillebrand
路
3Comments
davterra
路
3Comments
Most helpful comment
After the release, we should write an article on the blog that summarizes the changelog even for those who are not technical, talk about the contribution game, etc.
We should do this for every release, like btcpay blog. I find it very useful because it summarizes the changes that have taken place in the last months in a few lines.