Re: branch staging updated: gnu: ghc-7: Clean up package definition.

[Jakub Kądziołka]

On Tue, Jun 02, 2020 at 10:19:20PM +0200, Marius Bakke wrote:
> Jakub Kądziołka <kuba@kadziolka.net> writes:
> 
> > On Tue, Jun 02, 2020 at 09:22:31PM +0200, Marius Bakke wrote:
> >> We should have a better way to poll branch status other than "read all
> >> messages on guix-devel" or "ask Marius on IRC".
> >
> > Ouch, sorry for that! I see two potential solutions:
> >
> > 1. Have a guix-devel-announce mailing list, to which we would post
> >    things concerning all Guix developers.
> 
> Actually we already have an underutilized 'info-guix' list.  I suppose
> that can work.

Huh, I thought this was for communicating to Guix users.

> > 2. Configure the git server to reject pushes to frozen branches when
> >    unless --force is used.
> 
> It will be difficult for the server to distinguish between 'bug fixes'
> and 'huge rebuilds'.  Not sure if the --force flag propagates to servers
> the way you are thinking of, but perhaps it can work (not a great habit
> though!).

From the various behaviors of git servers I have observed, I would be
really surprised if it wasn't...

> Also, we'd have to bother the Savannah admins every time we 'freeze' a
> branch.

I suppose we could have a dotfile in the repository...

> Another option could be to create a tracking bug with a special tag that
> can be displayed by issues.guix.gnu.org.  It could also show any merge
> blockers such as <https://issues.guix.gnu.org/issue/41598> to make it
> easier to contribute.

Makes sense. We'd need to update the Commit Access section accordingly.

Regards,
Jakub Kądziołka

signature.asc
Description: PGP signature