From: John Kehayias <john.kehayias@protonmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: Katherine Cox-Buday <cox.katherine.e@gmail.com>, guix-devel@gnu.org
Subject: Re: Branch (and team?) for mesa updates
Date: Wed, 05 Jul 2023 20:12:12 +0000 [thread overview]
Message-ID: <87h6qiktig.fsf@protonmail.com> (raw)
In-Reply-To: <ZKWxibEJ1FPWpS3G@jurong>
Hello,
On Wed, Jul 05, 2023 at 08:08 PM, Andreas Enge wrote:
> Am Wed, Jul 05, 2023 at 09:47:06AM -0600 schrieb Katherine Cox-Buday:
>> I disagree with this because it seems like Mesa moves along at a pretty
>> brisk pace and I feel like we'd be constantly recreating the same branch:
>> 23.1.3, 2023-06-22 (14 days)
>> 23.1.2, 2023-06-08 ( 9 days)
>> 23.0.4, 2023-05-30 ( 5 days)
>> 23.1.1, 2023-05-25 (15 days)
>> 23.1.0, 2023-05-10
>
> I doubt we would be able to move at such a brisk pace and update mesa
> every other week! It is a package with more than 4000 dependents, so in
> any case it would be good to regroup with somewhat related changes.
>
Since the Cuirass job remains, I don't think it is really any extra
work or not to recreate the branch as needed, if that is preferred.
I'll defer to whatever people want, we can always change our mind if
anything comes up.
As for the pace, on the main 23.1.x releases we see about 2 weeks
currently. If that is a bit fast I think about once a month is a
reasonable pace, maybe depending if it is a small bugfix release or
what other changes we may need causing other rebuilds to be grouped on
the branch. We can slow down if major changes are introduced, but
seems Mesa is moving along without breaking changes or major changes
in building/support these days.
As you can follow along on <https://issues.guix.gnu.org/64369> within a
couple of days x86_64 and i686 had good weather (though I can't see
specifically what may have broken yet) while as we'd expect things
like aarch64 are still churning away. The speed of this build job
might determine how fast we can go anyway, but waiting too long will
mean a new minor release to build :)
John
next prev parent reply other threads:[~2023-07-05 20:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 18:25 Branch (and team?) for mesa updates John Kehayias
2023-07-02 10:30 ` Andreas Enge
2023-07-05 15:47 ` Katherine Cox-Buday
2023-07-05 18:08 ` Andreas Enge
2023-07-05 20:12 ` John Kehayias [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-29 16:12 John Kehayias
2023-07-31 1:50 ` Maxim Cournoyer
2023-08-26 0:50 ` John Kehayias
2023-08-26 19:52 ` Maxim Cournoyer
2023-08-27 4:45 ` dan
2023-09-07 18:45 ` Tobias Platen
2023-06-30 15:56 John Kehayias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6qiktig.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=andreas@enge.fr \
--cc=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.