[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#49334] [PATCH] DRAFT website: Add page listing branches.
From: |
pelzflorian (Florian Pelz) |
Subject: |
[bug#49334] [PATCH] DRAFT website: Add page listing branches. |
Date: |
Sat, 3 Jul 2021 09:52:32 +0200 |
Hi Ludo,
On Fri, Jul 02, 2021 at 06:29:04PM +0200, Ludovic Courtès wrote:
> Hi Guix!
>
> This is something we discussed at the last Guix Days: having a dashboard
> showing the active Git branches, their status, applicable constraints,
> and a target “freeze” date (one consensual proposal was that, instead of
> actually freezing the branch, we’d fork it as ‘BRANCH-frozen’ or something
> like that, leaving the branch open for further changes).
>
> This patch against guix-artwork.git is an attempt at providing a low-tech
> dashboard. I think it’s a good starting point, and certainly better than
> nothing. :-)
>
> What do people think?
I like it. Thank you!
> I’m also not sure what to do with
> menu entries. One last thing: we’ll need to list the ‘staging’ branch etc.
>
> Thoughts?
>
> Ludo’.
I don’t know, but maybe it should be in the About Guix menu on the
website?
Maybe the Guix manual should refer to https://guix.gnu.org/branches/ when
it is online?
> * website/apps/development/builder.scm,
> website/apps/development/data.scm:
> website/apps/development/templates/branches.scm,
> website/apps/development/templates/components.scm,
> website/static/development/css/branches.css: New files.
s/data.scm:/data.scm,/
> +++ b/website/apps/development/data.scm
> […]]
> +(define branches
> + (list (branch "master"
> + #:synopsis (G_ "Main development branch")
> + #:description
> + (G_
> + `(p "This is the main development branch, which "
> + (code "guix pull") " fetches by default. It should "
> + "contain only well-tested packages changes that do not "
> + "trigger more than 300 package rebuilds per "
> + "architecture. Run "
> + (code ,(G_ (manual-href "guix refresh -l"
> + (G_ "en")
> + (G_
> "Invoking-guix-refresh.html")))) " "
> + "for an estimate of the number of rebuilds triggered "
> + "by a package change.")))
> + (branch "core-updates"
> + #:synopsis (G_ "Changes to core packages and build tools")
> + #:description
> + (G_
> + `(p "This branch receives changes to core packages "
> + "that entail of most packages, and changes to "
s/entail of/entail/
Regards,
Florian