From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: monego@posteo.net, 56733@debbugs.gnu.org
Subject: bug#56733: Tryton LTS
Date: Sun, 24 Jul 2022 11:02:06 +0200 [thread overview]
Message-ID: <8b97cc65-fcc3-43b3-c2e2-53faee2a60d0@crazy-compilers.com> (raw)
In-Reply-To: <cd27b3ea0479062fb93d8955afba1797d43a189c.camel@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]
Follow-up to https://issues.guix.gnu.org/56706 „gnu: Tryton application
and framework: Update to 6.2.x.“.
Am 23.07.22 um 18:11 schrieb Vinicius Monego:
>> I'd suggest keeping Tryton at 6.0 to retain compatibility with GNU
>> Health, which tracks only the LTS versions of Tryton (minor versions
>> at
>> 0).
> To clarify a little further, GNU Health [1] (to keep it short, it is a
> set of health-related tryton modules) is not yet packaged in Guix. I
> did attempt to package it but got stuck in test errors in the check
> phase.
In general Guix is a rolling release distribution. Thus IMHO tryton
should be updated.
Anyhow I understand that we need a LTS variant for GNU Health and other
conservative users. We could create a „tryton-lts.scm“ which holds the
LTS versions, inherited from the current release. Creating such a file
is expected be to not much of a problem.
WDYT?
> The Tryton release process is explained in [2]. Normal releases have
> one year of support, while LTS releases have 5 years. Tryton has a huge
> package ecosystem and is mostly used in enterprise where LTS is more
> important. Tracking non-LTS releases would mean huge and breaking
> upgrades at least every year. Also 6.2 will be EOL in 3 months [2].
>
> [1]https://www.gnuhealth.org/
>
> [2]https://discuss.tryton.org/t/release-process/395
--
Regards
Hartmut Goebel
| Hartmut Goebel |h.goebel@crazy-compilers.com |
|www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 2719 bytes --]
next parent reply other threads:[~2022-07-24 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1658504593.git.h.goebel@crazy-compilers.com>
[not found] ` <1037a264876fa6aef19de72e406cea6c6a9040b3.camel@posteo.net>
[not found] ` <cd27b3ea0479062fb93d8955afba1797d43a189c.camel@posteo.net>
2022-07-24 9:02 ` Hartmut Goebel [this message]
2022-08-10 8:27 ` bug#56733: Tryton LTS Hartmut Goebel
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=8b97cc65-fcc3-43b3-c2e2-53faee2a60d0@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=56733@debbugs.gnu.org \
--cc=monego@posteo.net \
/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).