Re: Proposed changes to the commit policy

On Mon, Jan 30, 2023 at 10:40:42PM +0100, Ludovic Courtès wrote: > Hi! > > My 2¢ on this… As a committer & reviewer, I love that I can just go to > , pick one of the patch series with a > green tick, and have the assurance that the resource-intensive work is > alr

Re: Proposed changes to the commit policy (#59513)

Am Mon, Jan 30, 2023 at 10:03:14PM + schrieb Christopher Baines: > changes happen more slowly, but this is why I'm working on the tools and > processes, as I think that's a path to trying to maintain and improve > the quality while reducing the impact to pace and enjoyment. > I'm sure there are

Re: Proposed changes to the commit policy (#59513)

Hi, On Mon, 30 Jan 2023 at 22:03, Christopher Baines wrote: > In the past and currently to some extent, it's been possible to move > very quickly without comprimising on quality. However, my feeling on > this is that if we want to have quality support for non x86_64-linux > architectures, reprod

Re: Proposed changes to the commit policy (#59513)

Andreas Enge writes: > Am Wed, Jan 18, 2023 at 11:45:20AM + schrieb Christopher Baines: >> > as a quick concrete question: Do simple package updates still count as >> > trivial, or do they need to go through the patches mailing list? >> My feeling on this is that "simple" package updates are

Re: Proposed changes to the commit policy

Hi! My 2¢ on this… As a committer & reviewer, I love that I can just go to , pick one of the patch series with a green tick, and have the assurance that the resource-intensive work is already done. That makes a big difference! As someone who submits patches, I r

Re: Proposed changes to the commit policy

Hello, Am Mon, Jan 23, 2023 at 10:24:56AM +0100 schrieb Simon Tournier: > > Am Wed, Jan 18, 2023 at 04:54:58PM + schrieb Kaelyn: > >> On a side note, I'd recently discovered the flag to pass. To have a > >>subject prefix like "[PATCH core-updates]" (as mentioned in the manual > >>for staging a

Re: Proposed changes to the commit policy (#59513)

> While I understand this “extra“ work is a burden, what would you suggest > to reduce the number of broken packages? Because all the red circles in > the dashboard [2] is a strong issue, IMHO. some random 0.02 follows from a non-committer. i don't think this would be a lot of extra burden, but

Re: Proposed changes to the commit policy (#59513)

Hi Andreas, On Sun, 22 Jan 2023 at 18:18, Andreas Enge wrote: > So I tried it once, and find the hassle offputting. It feels like doubling > the effort - after doing the real work, I need to get back to it a week > later and more or less go through the motions again (rebase the commit > and resi

Re: Proposed changes to the commit policy (#59513)

Am Wed, Jan 18, 2023 at 11:45:20AM + schrieb Christopher Baines: > > as a quick concrete question: Do simple package updates still count as > > trivial, or do they need to go through the patches mailing list? > My feeling on this is that "simple" package updates are often not > trivial, or at l

Re: Proposed changes to the commit policy (#59513)

Hi Andreas, On mer., 18 janv. 2023 at 12:23, Andreas Enge wrote: > as a quick concrete question: Do simple package updates still count as > trivial, or do they need to go through the patches mailing list? > I intended to update pari-gp from 2.15.1 to 2.15.2, as usual by checking > that all depen

Re: Proposed changes to the commit policy (#59513)

--- Original Message --- On Wednesday, January 18th, 2023 at 11:45 AM, Christopher Baines wrote: > > Andreas Enge andr...@enge.fr writes: > > > Hello, > > > > Am Mon, Jan 16, 2023 at 09:47:06PM + schrieb Christopher Baines: > > > > > I merged the changes a few days ago, so this is

Re: Proposed changes to the commit policy (#59513)

Andreas Enge writes: > Hello, > > Am Mon, Jan 16, 2023 at 09:47:06PM + schrieb Christopher Baines: >> I merged the changes a few days ago, so this is just a quick message to >> say that the commit policy has changed. You can read the updated policy >> here: >> >> https://guix.gnu.org/en/m

Re: Proposed changes to the commit policy (#59513)

Hello, Am Mon, Jan 16, 2023 at 09:47:06PM + schrieb Christopher Baines: > I merged the changes a few days ago, so this is just a quick message to > say that the commit policy has changed. You can read the updated policy > here: > > https://guix.gnu.org/en/manual/devel/en/html_node/Commit-Ac

Re: Proposed changes to the commit policy (#59513)

Hello, Christopher Baines skribis: > I merged the changes a few days ago, so this is just a quick message to > say that the commit policy has changed. You can read the updated policy > here: > > > https://guix.gnu.org/en/manual/devel/en/html_node/Commit-Access.html#Commit-Policy Nice, thanks

Re: Proposed changes to the commit policy (#59513)

Christopher Baines writes: > A few weeks back, I sent a patch with some changes to the commit policy [1]: > > https://issues.guix.gnu.org/59513 > > There's already been some feedback and revisions which is great. The > policy also suggests guix-devel as a place for discussions regarding the >