all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vinicius Monego <monego@posteo.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>, 56706@debbugs.gnu.org
Subject: [bug#56706] [PATCH 00/17] Update Tryton to 6.2.
Date: Sat, 23 Jul 2022 16:11:28 +0000	[thread overview]
Message-ID: <cd27b3ea0479062fb93d8955afba1797d43a189c.camel@posteo.net> (raw)
In-Reply-To: <1037a264876fa6aef19de72e406cea6c6a9040b3.camel@posteo.net>

Em sex, 2022-07-22 às 15:27 -0300, Vinicius Monego escreveu:
> Em sex, 2022-07-22 às 17:45 +0200, Hartmut Goebel escreveu:
> > Update all existing Tryton packages to the latest 6.2.x version and
> > add the
> > latest version of all Tryton modules new in 6.2.
> > 
> > This needs to be applied after issue 56701.
> 
> Hi,
> 
> 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.

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




  reply	other threads:[~2022-07-23 16:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 15:45 [bug#56706] [PATCH 00/17] Update Tryton to 6.2 Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 01/17] gnu: Add python-pycountry@20.7.3 Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 02/17] gnu: Tryton application and framework: Update to 6.2.x Hartmut Goebel
2022-07-22 17:25   ` Maxime Devos
2022-07-24  8:51     ` Hartmut Goebel
2022-07-24  9:26       ` Maxime Devos
2022-07-22 15:47 ` [bug#56706] [PATCH 03/17] gnu: Add trytond-account-budget Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 04/17] gnu: Add trytond-account-move-line-grouping Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 05/17] gnu: Add trytond-account-rule Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 06/17] gnu: Add trytond-account-stock-shipment-cost Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 07/17] gnu: Add trytond-analytic-budget Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 08/17] gnu: Add trytond-currency-ro Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 09/17] gnu: Add trytond-currency-rs Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 10/17] gnu: Add trytond-product-image Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 11/17] gnu: Add trytond-product-image-attribute Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 12/17] gnu: Add trytond-sale-point Hartmut Goebel
2022-07-22 15:47 ` [bug#56706] [PATCH 13/17] gnu: Add trytond-stock-package-shipping-mygls Hartmut Goebel
2022-07-22 15:48 ` [bug#56706] [PATCH 14/17] gnu: Add trytond-stock-package-shipping-sendcloud Hartmut Goebel
2022-07-22 15:48 ` [bug#56706] [PATCH 15/17] gnu: Add python-pyactiveresource Hartmut Goebel
2022-07-22 15:48 ` [bug#56706] [PATCH 16/17] gnu: Add python-shopifyapi Hartmut Goebel
2022-07-22 15:48 ` [bug#56706] [PATCH 17/17] gnu: Add trytond-web-shop-shopify Hartmut Goebel
2022-07-22 18:27 ` [bug#56706] [PATCH 00/17] Update Tryton to 6.2 Vinicius Monego
2022-07-23 16:11   ` Vinicius Monego [this message]
2022-07-24  9:02     ` bug#56733: Tryton LTS Hartmut Goebel
2022-08-10  8:27       ` Hartmut Goebel
2022-07-24  9:08   ` [bug#56706] [PATCH 00/17] Update Tryton to 6.2 Hartmut Goebel
     [not found] ` <handler.56706.B.165850477414349.ack@debbugs.gnu.org>
2022-08-10 12:28   ` bug#56706: Acknowledgement ([PATCH 00/17] Update Tryton to 6.2.) 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

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

  git send-email \
    --in-reply-to=cd27b3ea0479062fb93d8955afba1797d43a189c.camel@posteo.net \
    --to=monego@posteo.net \
    --cc=56706@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.