Re: core-updates schedule

Hello, Marius Bakke skribis: > Ricardo Wurmus writes: > >> Ludovic Courtès writes: >> >>> Today I’ll try switching to glibc 2.28, and if it works well, I’d like >>> to make it the last big change in ‘core-updates’. >> >> Marius was working glibc 2.28 and that was the last big change I wanted

Re: core-updates schedule

Ricardo Wurmus writes: > Ludovic Courtès writes: > >> Today I’ll try switching to glibc 2.28, and if it works well, I’d like >> to make it the last big change in ‘core-updates’. > > Marius was working glibc 2.28 and that was the last big change I wanted > to allow into core-updates. I don’t

Re: core-updates schedule

Ludovic Courtès writes: > Hi there! > > Ricardo Wurmus skribis: > >> Ricardo Wurmus writes: > > [...] > >>> This is a reminder about the “core-updates” branch. Our plan was to >>> freeze the branch on <2018-08-06 Mon> and aim to merge the branch into >>> “master” on <2018-08-20 Mon>,

Re: core-updates schedule

Hi there! Ricardo Wurmus skribis: > Ricardo Wurmus writes: [...] >> This is a reminder about the “core-updates” branch. Our plan was to >> freeze the branch on <2018-08-06 Mon> and aim to merge the branch into >> “master” on <2018-08-20 Mon>, dependent on how long it takes to fix all >>

Re: core-updates schedule

Ricardo Wurmus writes: > Hello Guix! > > This is a reminder about the “core-updates” branch. Our plan was to > freeze the branch on <2018-08-06 Mon> and aim to merge the branch into > “master” on <2018-08-20 Mon>, dependent on how long it takes to fix all > problems and build most packages. >

Re: core-updates schedule

Hi Efraim, Efraim Flashner writes: > Does core-updates currently address bug 31974, aka 'phases should return > #t or actually fail'? Thanks for the reminder. I just pushed a fix for this to core-updates, commit 82230603ce06de7aa3e4aef2fa093a6dbf0ef8df. Mark

Re: core-updates schedule

On Wed, Aug 01, 2018 at 08:41:00PM +0200, Ricardo Wurmus wrote: > Hello Guix! > > This is a reminder about the “core-updates” branch. Our plan was to > freeze the branch on <2018-08-06 Mon> and aim to merge the branch into > “master” on <2018-08-20 Mon>, dependent on how long it takes to fix all

core-updates schedule

Hello Guix! This is a reminder about the “core-updates” branch. Our plan was to freeze the branch on <2018-08-06 Mon> and aim to merge the branch into “master” on <2018-08-20 Mon>, dependent on how long it takes to fix all problems and build most packages. Freezing the branch means that only

Re: ‘core-updates’ schedule

Leo Famulari transcribed 1.1K bytes: > On Thu, Apr 06, 2017 at 10:34:29AM +0200, Ludovic Courtès wrote: > > This ‘core-updates’ cycle was terribly long, so I suggest to write down > > a schedule and then try hard to stick to it. ;-) > > At the beginning of the cycle, I was confident that we

Re: ‘core-updates’ schedule

Heya! Leo Famulari skribis: > On Thu, Apr 06, 2017 at 10:34:29AM +0200, Ludovic Courtès wrote: >> This ‘core-updates’ cycle was terribly long, so I suggest to write down >> a schedule and then try hard to stick to it. ;-) > > At the beginning of the cycle, I was confident

Re: ‘core-updates’ schedule

On Thu, Apr 06, 2017 at 10:34:29AM +0200, Ludovic Courtès wrote: > This ‘core-updates’ cycle was terribly long, so I suggest to write down > a schedule and then try hard to stick to it. ;-) At the beginning of the cycle, I was confident that we could build and merge it in 2 or 3 weeks. But, it

‘core-updates’ schedule

Hello Guix! This ‘core-updates’ cycle was terribly long, so I suggest to write down a schedule and then try hard to stick to it. ;-) What about this: • May 25th, ‘core-updates’ branch frozen (i.e., rebuild-the-world changes are no longer accepted); • June 15th, ‘core-updates’ merged