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.

Sign up for GitHub

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

Jump to bottom

release: Refine process #1176

Closed
real-or-random opened this issue Dec 12, 2022 · 4 comments · Fixed by #1310
Closed

release: Refine process #1176

real-or-random opened this issue Dec 12, 2022 · 4 comments · Fixed by #1310
Milestone
0.4.0

Comments

@real-or-random
Copy link
Contributor

Some questions that popped up during the 0.2.0 release:

  • Maintenance release: In fact we could have multiple PRs here before the release PR. Do we want to write this down?
  • Should we add instructions to check the contents of make dist / run make distcheck?
  • Add instructions to run symbol check (after Add tools/symbol-check.py #1135)?
@real-or-random real-or-random mentioned this issue Dec 12, 2022
Closed
@hebasto
Copy link
Member

hebasto commented Dec 13, 2022

👍

@real-or-random
Copy link
Contributor Author

Release schedule (from IRC meeting 2023-01-16):

  • Twice as often as a major release of Core (which is every 6-7 months), i.e., every 3-4 months for us. We try to aim to one month before feature freeze of Core major release for every second of our releases. Of course, we can still create more releases whenever we feel there's need, e.g., for bugfixes.
  • That means the next planned release will be on/around 2023-03-01.

@real-or-random real-or-random mentioned this issue Mar 7, 2023
Merged
@real-or-random
Copy link
Contributor Author

Another thing that's good to sanity-check before release (even if done manually) is if the result of make install looks reasonable (e.g., set of files is correct). This can be done best with by installing to some temporary location, i.e., --prefix=/tmp/install or -DCMAKE_INSTALL_PREFIX=/tmp/install.

@real-or-random
Copy link
Contributor Author

We should think about signing releases properly.

@jonasnick jonasnick mentioned this issue May 12, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.4.0
Development

Successfully merging a pull request may close this issue.

Refine release process jonasnick/secp256k1
2 participants
@real-or-random @hebasto