From: "iank at fsf dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29643] Release upload process improvements
Date: Wed, 12 Oct 2022 04:07:08 +0000 [thread overview]
Message-ID: <bug-29643-14326-vD8v0hy0zF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29643-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29643
iank at fsf dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iank at fsf dot org
--- Comment #3 from iank at fsf dot org ---
Update: A volunteer, Jacob Bachmeyer, is working on doing some
documenting and refactoring so it is reasonable for anyone to adopt and
use instead of just the GNU release site. For example having a
documented config file instead of hard coded variables with path
locations. His estimate for this is a few weeks to a month or three, and
I prefer to wait to publish it until then. But as I said before, if you
want is sooner, just ask and I can provide it privately under GPLv3+ in
it's current state and then of course you have the freedom to share as
you wish.
I will definitely add a pointer on this bug when we publish it.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-10-12 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 21:17 [Bug Infrastructure/29643] New: " mark at klomp dot org
2022-10-03 3:10 ` Ian Kelling
2022-10-03 17:10 ` Frank Ch. Eigler
2022-10-07 15:38 ` Ian Kelling
2022-10-03 4:08 ` [Bug Infrastructure/29643] " iank at fsf dot org
2022-10-06 17:50 ` mark at klomp dot org
2022-10-12 4:07 ` iank at fsf dot org [this message]
2022-12-31 16:14 ` mark at klomp dot org
2023-01-04 11:14 ` Ian Kelling
2023-01-04 11:14 ` iank at fsf dot org
2023-01-10 9:51 ` iank at fsf dot org
2023-01-10 10:04 ` iank at fsf dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-29643-14326-vD8v0hy0zF@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).