Skip to content

Update README.md #9

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

Merged
merged 1 commit into from
Sep 19, 2024
Merged

Update README.md #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,12 +13,12 @@ fragmentation. We will update this readme if those design choices change.

zph fork will use release naming in the following form:

v3.0.62-20240705-3c7af6a
v3.0.62005

{petoju version}-{date}-{sha}
{petoju version}{sequential int of additional applied patches}

This indicates that the base is v3.0.62 from petoju, with modifications from zph
repo using {sha} and built on {date}.
repo that are 5 patch sets added.

It allows for keeping patches alive on this fork until they land upstream and are
released there.
Expand All @@ -27,7 +27,9 @@ released there.

We sign releases with a GPG key currently using goreleaser locally on the personal
equipment of @ZPH. As the maintainer of this fork, I, @ZPH, attest that the builds
represent the exact SHA of the version control with no alterations.
represent the exact SHA of the version control with no alterations. The credentials
are stored in a credential manager with layers of safeguards and no other individuals
have access.

The near term goal is to setup github actions to provide this guarantee
so that even if I were a malicious actor or coerced,
Expand Down