From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 49334@debbugs.gnu.org
Subject: [bug#49334] [PATCH] DRAFT website: Add page listing branches.
Date: Thu, 08 Jul 2021 10:20:33 +0200 [thread overview]
Message-ID: <871r89md2m.fsf@gnu.org> (raw)
In-Reply-To: <87a6mzwx2j.fsf@gnu.org> (Mathieu Othacehe's message of "Tue, 06 Jul 2021 12:33:56 +0200")
Hello!
Mathieu Othacehe <othacehe@gnu.org> skribis:
>> + #:target-date (string->date* "2021-07-20")
>> + #:merge-period (* 4 30 24 3600))))
>
> This looks fine, thanks! I wonder if it would make sense to extract the
> target date and maybe other information from Cuirass.
>
> We could have something like specification properties with a key/value
> association. The https://ci.guix.gnu.org/specification/master/properties
> URL would return:
>
> {
> TARGET_DATE: "2021-07-20"
> }
>
> This way, the https://guix.gnu.org/branches page would be mostly static
> and we could update specification properties directly from Cuirass web
> interface.
Ah, that’s an interesting idea. This would be a key/value property list
that Cuirass wouldn’t touch, right?
I kinda liked the idea of having the target date automatically repeat,
whether or not we’re on time :-), but maybe what you suggest would be
more reasonable.
That said, if /properties returns JSON, we cannot make the page static,
unless we add JS code to fetch /properties and to present it nicely,
right?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-07-08 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 16:29 [bug#49334] [PATCH] DRAFT website: Add page listing branches Ludovic Courtès
2021-07-03 7:52 ` pelzflorian (Florian Pelz)
2021-07-06 10:33 ` Mathieu Othacehe
2021-07-08 8:20 ` Ludovic Courtès [this message]
2021-07-08 12:00 ` Mathieu Othacehe
2021-07-09 14:04 ` Ludovic Courtès
2022-06-12 8:39 ` Ricardo Wurmus
2024-01-24 22:17 ` bug#49334: " Ludovic Courtès
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=871r89md2m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=49334@debbugs.gnu.org \
--cc=othacehe@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.