Github messages for voidlinux
 help / color / mirror / Atom feed
From: martnnw <martnnw@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: blender: update to 2.83.5
Date: Thu, 10 Sep 2020 21:14:04 +0200	[thread overview]
Message-ID: <20200910191404.Xvme2AKpHxKyQKbWmitqfZffbEqXeupHAiWDUzD1xEw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24644@inbox.vuxu.org>

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

New comment by martnnw on void-packages repository

https://github.com/void-linux/void-packages/pull/24644#issuecomment-690610619

Comment:
The LTS versions are intended for larger organizations that work on bigger projects such as feature films and therefore need a version that is dependable and does not break when new features are introduced. Constant breakage could lead to unnecessary production costs. 

It's unlikely that we have void-users who work in the CG industry, therefore 2.90 is probably the better option if you favor supporting only one version. However maintaining LTS version probably won't be too difficult as they will only receive occasional bug-fixes.

  parent reply	other threads:[~2020-09-10 19:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 19:27 [PR PATCH] " jkoderu-git
2020-09-09 16:43 ` [PR PATCH] [Updated] " jkoderu-git
2020-09-09 20:31 ` martnnw
2020-09-10 14:46 ` jkoderu-git
2020-09-10 14:50 ` [PR PATCH] [Updated] " jkoderu-git
2020-09-10 14:52 ` martnnw
2020-09-10 14:53 ` martnnw
2020-09-10 14:53 ` martnnw
2020-09-10 14:58 ` martnnw
2020-09-10 14:58 ` martnnw
2020-09-10 15:45 ` ahesford
2020-09-10 17:00 ` [PR PATCH] [Updated] " jkoderu-git
2020-09-10 18:39 ` martnnw
2020-09-10 19:14 ` martnnw [this message]
2020-09-10 19:14 ` martnnw
2020-09-24 16:03 ` [PR PATCH] [Closed]: " Johnnynator
2020-09-24 16:04 ` Johnnynator

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=20200910191404.Xvme2AKpHxKyQKbWmitqfZffbEqXeupHAiWDUzD1xEw@z \
    --to=martnnw@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).