Re: Questions on Managing Patches and Branches

2025-03-29 Thread Development of GNU Guix and the GNU System distribution.
Hello, Andreas Enge writes: > Hello Chris, > > Am Fri, Mar 28, 2025 at 10:31:26PM +0300 schrieb Christopher Baines: >> On tooling, as I say, QA used to attempt to build the first 2 or 3 >> branches. With the data service and build coordination being a bit >> faster now, I think building the firs

Re: Questions on Managing Patches and Branches

2025-03-29 Thread Andreas Enge
Hello Chris, Am Fri, Mar 28, 2025 at 10:31:26PM +0300 schrieb Christopher Baines: > On tooling, as I say, QA used to attempt to build the first 2 or 3 > branches. With the data service and build coordination being a bit > faster now, I think building the first two branches might be > feasible. Tha

Re: Questions on Managing Patches and Branches

2025-03-28 Thread Christopher Baines
Greg Hogan writes: > How "ready" do branches need to be in the "request to merge" queue? The relevant bit is: To help coordinate the merging of branches, you must create a new guix-patches issue each time you create a branch (see The Issue Tracker). From [1], the rational was to combine

Questions on Managing Patches and Branches

2025-03-28 Thread Greg Hogan
How "ready" do branches need to be in the "request to merge" queue? Our documentation [0] includes both of the following statements: "Once a branch is at the front of the queue, wait until sufficient time has passed for the build farms to have processed the changes, and for the necessary testing t