Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Organization requirements
Date: Fri, 24 Apr 2020 14:08:44 +0200	[thread overview]
Message-ID: <20200424120844.hg2i3ydqEv-WlBHIvpz5vFb2GJN44iIflNLGjHcVfsA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21299@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/issues/21299#issuecomment-618971353

Comment:
- I'm OK with the relaxing for non-critical package
- I think those packages in bootstrap list or the one that have equivalent in bootstrap should be reviewed by more people. E.g: I don't want to push nss, git out when noone else tested it. If that package was written by that maintainer, it's a different story.
- For the security update, I don't think we should wait. Fast track is OK to me.
- If the package is causing broken in buildbot, I expect someone fast-track either a fix, revert (with at least some testing) or make it broken.

  parent reply	other threads:[~2020-04-24 12:08 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 11:32 [ISSUE] " xtraeme
2020-04-24 11:39 ` xtraeme
2020-04-24 11:45 ` Duncaen
2020-04-24 11:46 ` Duncaen
2020-04-24 11:48 ` xtraeme
2020-04-24 11:48 ` xtraeme
2020-04-24 11:49 ` xtraeme
2020-04-24 11:50 ` leahneukirchen
2020-04-24 11:51 ` xtraeme
2020-04-24 11:52 ` xtraeme
2020-04-24 11:57 ` xtraeme
2020-04-24 11:57 ` leahneukirchen
2020-04-24 11:59 ` xtraeme
2020-04-24 12:01 ` xtraeme
2020-04-24 12:01 ` xtraeme
2020-04-24 12:08 ` sgn [this message]
2020-04-24 12:11 ` sgn
2020-04-24 12:11 ` xtraeme
2020-04-24 12:12 ` xtraeme
2020-04-24 12:21 ` xtraeme
2020-04-24 12:22 ` xtraeme
2020-04-24 13:07 ` pullmoll
2020-04-24 13:09 ` pullmoll
2020-04-24 13:13 ` xtraeme
2020-04-24 14:05 ` Vaelatern
2020-04-24 14:27 ` xtraeme
2020-04-24 14:34 ` q66
2020-04-24 15:09 ` xtraeme
2020-04-24 15:15 ` xtraeme
2020-04-24 15:16 ` Anachron
2020-04-24 15:25 ` xtraeme
2020-04-24 15:25 ` [ISSUE] [CLOSED] " xtraeme
2020-04-24 15:33 ` Anachron
2020-04-24 19:02 ` Mothrakk
2020-04-24 19:32 ` rugalash
2020-04-24 19:33 ` the-maldridge

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=20200424120844.hg2i3ydqEv-WlBHIvpz5vFb2GJN44iIflNLGjHcVfsA@z \
    --to=sgn@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).