Hello!
For the record, I created a few days ago an issue to keep track of
progress towards the release by blocking it with issues that we think
must be fixed before we release:
https://issues.guix.gnu.org/53214
Click on “Details” to see the blocking issues.
Hopefully it’ll allow everyone of
Hi Chris,
Chris Marusich writes:
[...]
> With Ludo's feedback, I was able to fix 52940 without rebuilding the
> world in commit 195bb1fb9d55d8e5187d669c63a3cde747fc5f64 on master. Can
> you try merging master into your version-1.4.0 branch?
Awesome! As you may have noticed, today
On 2021-12-26, Maxim Cournoyer wrote:
> Vagrant Cascadian writes:
>> On 2021-12-19, Maxim Cournoyer wrote:
>>> zimoun writes:
Now core-updates-frozen is merged. Now The Big Change [1 ]is done. Do
we go for v1.4 or v2.0?
...
>> Would it be appropriate to fix the ~700 low-hanbging
Hi Maxim,
Maxim Cournoyer writes:
> Hello Chris,
>
> Chris Marusich writes:
>
>> Maxim Cournoyer writes:
>>
>>> About the current status, I'm nearing on pushing a version-1.4.0 branch
>>> which is based on master with a few more (core-ish) updates. There's
>>> still a few days ahead of that,
Hello Chris,
Chris Marusich writes:
> Maxim Cournoyer writes:
>
>> About the current status, I'm nearing on pushing a version-1.4.0 branch
>> which is based on master with a few more (core-ish) updates. There's
>> still a few days ahead of that, so if you manage to get many of this
>> kind of
Maxim Cournoyer writes:
> About the current status, I'm nearing on pushing a version-1.4.0 branch
> which is based on master with a few more (core-ish) updates. There's
> still a few days ahead of that, so if you manage to get many of this
> kind of problems fixed & merged in master they can
Hello,
Ludovic Courtès writes:
> Hello!
>
> Maxim Cournoyer skribis:
>
>> About the current status, I'm nearing on pushing a version-1.4.0 branch
>> which is based on master with a few more (core-ish) updates. There's
>> still a few days ahead of that, so if you manage to get many of this
>>
On 2022-01-03, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>> On 2021-12-21, Vagrant Cascadian wrote:
>
> [...]
>
>>> Would it be appropriate to fix the ~700 low-hanbging fruit issues that
>>> are identified by:
>>>
>>> guix lint --checkers=description,synopsis
>
> [...]
>
>> Could guix
Hello!
Maxim Cournoyer skribis:
> About the current status, I'm nearing on pushing a version-1.4.0 branch
> which is based on master with a few more (core-ish) updates. There's
> still a few days ahead of that, so if you manage to get many of this
> kind of problems fixed & merged in master
Hello!
Vagrant Cascadian skribis:
> On 2021-12-21, Vagrant Cascadian wrote:
[...]
>> Would it be appropriate to fix the ~700 low-hanbging fruit issues that
>> are identified by:
>>
>> guix lint --checkers=description,synopsis
[...]
> Could guix style be adapted to apply some of these
Hi Vagrant,
Vagrant Cascadian writes:
> On 2021-12-19, Maxim Cournoyer wrote:
>> zimoun writes:
>>> Now core-updates-frozen is merged. Now The Big Change [1 ]is done. Do
>>> we go for v1.4 or v2.0?
>>
>> As I've mentioned previously, I'd go for a 1.4.0 release, since overall
>> we've refined
On 2021-12-21, Vagrant Cascadian wrote:
> On 2021-12-19, Maxim Cournoyer wrote:
>> zimoun writes:
>>> In both case, what is the target for a release date? I propose January
>>> 31rst. WDYT?
>>
>> I'd like to fix #52051 before issuing the first release candidate (RC).
>> Assuming this can be
On 2021-12-19, Maxim Cournoyer wrote:
> zimoun writes:
>> Now core-updates-frozen is merged. Now The Big Change [1 ]is done. Do
>> we go for v1.4 or v2.0?
>
> As I've mentioned previously, I'd go for a 1.4.0 release, since overall
> we've refined and improved (greatly!) what we already had
Hi,
On Mon, 20 Dec 2021 at 22:24, Ludovic Courtès wrote:
> Same here. But first it’d be nice to come up with a summary of what we
> did in ‘core-updates’ because I think we’ve all forgotten most of it.
> :-)
A summary as a ChangeLog or a summary as a blog post? :-)
Cheers,
simon
Hi,
zimoun skribis:
> On Sun, 19 Dec 2021 at 21:12, Maxim Cournoyer
> wrote:
>> zimoun writes:
>
>>> Now core-updates-frozen is merged. Now The Big Change [1 ]is done. Do
>>> we go for v1.4 or v2.0?
>>
>> As I've mentioned previously, I'd go for a 1.4.0 release, since overall
>> we've
Hi all,
On +2021-12-19 21:12:36 -0500, Maxim Cournoyer wrote:
> Hi Simon,
>
> zimoun writes:
>
> > Hi,
> >
> > Now core-updates-frozen is merged. Now The Big Change [1 ]is done. Do
> > we go for v1.4 or v2.0?
>
> As I've mentioned previously, I'd go for a 1.4.0 release, since overall
>
On Mon, 20 Dec 2021 at 10:04, zimoun wrote:
>> I'd like to fix #52051 before issuing the first release candidate (RC).
>> Assuming this can be made before the end of January with the first RC
>> coming out around New Year, and that the kind of collaboration I've seen
>> in the last weeks
Hi Maxim,
On Sun, 19 Dec 2021 at 21:12, Maxim Cournoyer wrote:
> zimoun writes:
>> Now core-updates-frozen is merged. Now The Big Change [1 ]is done. Do
>> we go for v1.4 or v2.0?
>
> As I've mentioned previously, I'd go for a 1.4.0 release, since overall
> we've refined and improved
On Sun, 19 Dec 2021 21:12:36 -0500
Maxim Cournoyer wrote:
> Hi Simon,
>
> zimoun writes:
>
> > Hi,
> >
> > Now core-updates-frozen is merged. Now The Big Change [1 ]is done.
> > Do we go for v1.4 or v2.0?
>
> As I've mentioned previously, I'd go for a 1.4.0 release, since
> overall we've
Hi Simon,
zimoun writes:
> Hi,
>
> Now core-updates-frozen is merged. Now The Big Change [1 ]is done. Do
> we go for v1.4 or v2.0?
As I've mentioned previously, I'd go for a 1.4.0 release, since overall
we've refined and improved (greatly!) what we already had rather than
introduced
20 matches
Mail list logo
