git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 2/2] Document how we do embargoed releases - improving mail template

From
Robin H. Johnson <robbat2@gentoo.org>
Date
Apr 20, 2021, 22:45 UTC
Message-ID
<robbat2-20210420T223619-939869983Z@orbis-terrarum.net>
In-Reply-To
<xmqq5z0g4oc9.fsf@gitster.g>
On Tue, Apr 20, 2021 at 02:51:02PM -0700, Junio C Hamano wrote:
Show 17 quoted lines
> "Robin H. Johnson" <robbat2@gentoo.org> writes:
> > As one of the Gentoo maintainer for Git, I was wondering if the
> > embargoed-releases process could be tweaked slightly.
> >
> > Specifically, in the embargo email, could you please publishing the
> > exact size & digests of the to-be-released tarballs, esp. the htmldocs &
> > manpages tarballs.
> 
> HTMLdocs and Manpages are as far as I am concerned part of SOURCES.
> 
> They are generated from the true sources, I do not give signed tags
> to them, and as a source-based distribution, Gentoo shouldn't
> consider them as such, either.  When release tags are signed, their
> sizes or digests are simply unavailable, since they have not even
> been generated yet (I tag the releases, run make in the tagged
> release tarball extract and that is what is tarred up as HTMLdocs
> and or Manpages).

I didn't say that those tarballs were tagged independently, as your mail seems to imply.

As part of the embargo process, you're sending the tags out already. All 3 tarballs are artifacts derived from those tags, directly or indirectly, and you presumably have the same process to generate the final tarballs if the tags are embargoed or not. I'm just asking that the final tarballs are generated when the tags are, and the sizes & digests of the tarballs are shared in the embargo email.

Alternatively, publish byte-exact reproduction steps from the tags to the tarballs, so that we can generate them locally for co-ordinated release.

-- 
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
E-Mail   : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
Previous: Junio C HamanoNext: Junio C Hamano
Message 12 of 15 in “Describe Git's security policy”
  1. 0/2 Describe Git's security policyJohannes Schindelin via GitGitGadget, Mar 26, 2021
  2. 2/2 Document how we do embargoed releasesJohannes Schindelin via GitGitGadget, Mar 26, 2021
  3. 1/2 SECURITY: describe how to report vulnerabilitiesJohannes Schindelin via GitGitGadget, Mar 26, 2021
  4. Denton LiuMar 27, 2021
  5. Johannes SchindelinMar 29, 2021
  6. Bagas SanjayaMar 27, 2021
  7. Johannes SchindelinMar 29, 2021
  8. 0/2 Describe Git's security policyJohannes Schindelin via GitGitGadget, Mar 29, 2021
  9. 2/2 Document how we do embargoed releasesJohannes Schindelin via GitGitGadget, Mar 29, 2021
  10. Robin H. JohnsonApr 20, 2021
  11. Junio C HamanoApr 20, 2021
  12. Robin H. JohnsonApr 20, 2021
  13. Junio C HamanoApr 20, 2021
  14. Junio C HamanoApr 20, 2021
  15. 1/2 SECURITY: describe how to report vulnerabilitiesJohannes Schindelin via GitGitGadget, Mar 29, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.