unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Tai <atai@atai.org>
To: guix-devel@gnu.org
Subject: Re: guix package updates review: app team?
Date: Fri, 27 Jan 2023 14:22:51 -0800	[thread overview]
Message-ID: <CAJsg1E8svYPRHM279-PvN0yZHqzkhcqmh4Ps8SFjiNZZK5OPNg@mail.gmail.com> (raw)
In-Reply-To: <CAJsg1E_XrADqnMk_HChRS8JbG7VTVakbb320qpb85mKmyrN-CA@mail.gmail.com>

last paragraph shall be

As application packages are usually at
the end of the dependency chain (they depend on other libraries or
components more than the other way around) updating application packages shall
take less review effort.

On Fri, Jan 27, 2023 at 2:19 PM Andy Tai <atai@atai.org> wrote:
>
> Hi, currently Guix has teams of reviewers for different types of
> packages.   For example, changes to R packages and emacs seem to be
> reviewed quickly.  However, recently, patches for updating more
> general application packages (octave, for example) seem to be reviewed
> and processed very slowly.
>
> As a GNU/Linux distribution the update speed of applications impact
> the perception of the community on a distribution, and thus it is
> beneficial if packages update can be processed quickly to keep Guix
> "up to date" so to speak.  Hope Guix maintainers can give some thought
> to this and let more volunteers participate in package review process
> to allow package updates more quickly.   As packages are usually at
> the end of the dependency chain (they depend on other libraries or
> components more than the other way around) updating packages shall
> take less review effort.



-- 
Andy Tai, atai@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat: andytai1010
Year 2023 民國112年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能


  reply	other threads:[~2023-01-27 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 22:19 guix package updates review: app team? Andy Tai
2023-01-27 22:22 ` Andy Tai [this message]
2023-01-30 12:06 ` Simon Tournier

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJsg1E8svYPRHM279-PvN0yZHqzkhcqmh4Ps8SFjiNZZK5OPNg@mail.gmail.com \
    --to=atai@atai.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).