Github messages for voidlinux
 help / color / mirror / Atom feed
From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: black: ignore alpha releases.
Date: Fri, 06 Jan 2023 16:11:18 +0100	[thread overview]
Message-ID: <20230106151118.iwUxm3TXTH1YDnWVb7BnmzWeMpZI2oFYBIme1OhSRXA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41481@inbox.vuxu.org>

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

New comment by mhmdanas on void-packages repository

https://github.com/void-linux/void-packages/pull/41481#issuecomment-1373753132

Comment:
Maybe, but back when beta releases for black were used, they were meant to convey the stability of black as a whole, not the stability of that specific release. However, after black was declared stable, beta releases were never used, so we don't know what they'll convey in the future in terms of stability of the release. As a result, I think it's better to be conservative and ignore only alpha releases until a sufficient reason to ignore beta releases too arises.

  parent reply	other threads:[~2023-01-06 15:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06  0:00 [PR PATCH] " mhmdanas
2023-01-06  6:43 ` icp1994
2023-01-06 15:11 ` mhmdanas [this message]
2023-01-06 15:11 ` mhmdanas
2023-01-07  2:10 ` [PR REVIEW] " Piraty
2023-01-07  2:10 ` Piraty
2023-01-10 13:47 ` mhmdanas
2023-04-08 14:59 ` mhmdanas
2023-06-26  1:14 ` classabbyamp
2023-06-26  1:15 ` classabbyamp
2023-06-26  9:34 ` mhmdanas
2023-06-26  9:38 ` classabbyamp
2023-06-26 14:53 ` mhmdanas
2023-06-26 14:53 ` mhmdanas
2023-06-26 19:53 ` [PR PATCH] [Updated] " mhmdanas
2023-06-26 19:53 ` [PR PATCH] [Updated] black: ignore alpha and beta releases mhmdanas
2023-06-26 20:04 ` [PR PATCH] [Merged]: " classabbyamp

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=20230106151118.iwUxm3TXTH1YDnWVb7BnmzWeMpZI2oFYBIme1OhSRXA@z \
    --to=mhmdanas@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).