unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: Contribute or create a channel?
Date: Fri, 01 Mar 2024 23:39:07 +0100	[thread overview]
Message-ID: <87y1b1shfm.fsf@elephly.net> (raw)
In-Reply-To: <ed02e829-2ff5-5b0f-9849-61b48465f17b@crazy-compilers.com>


Hi Hartmut,

> I'm currently updating Tryton to version 7.0 and am wondering whether it's better to contribute the change to Guix or to set up a
> channel for Tryton.
>
> WDYT? I'm eager to learn about your thoughts.
>
> Here is why I'm wondering:
>
> * Tryton consists of a client, a server and about 200 module/add-on providing business logic.
> * Tryton publishes a LTS version every 2.5 years. Two LTS versions are supported (currently 6.0 and 7.0) and bugfixes are backported
>  there for 5 years.

I think it would be preferable to have one LTS version in Guix.  If you
want to commit to maintaining the packages I think it would be worth
discussing whether to grant you commit rights to handle these upgrades
by yourself.

> OTOH in Guix, maintaining several version seems laborious.

What makes you say this?  What exactly is the obstacle here?

> Anyhow I'm unsure whether it's worth the effort maintaining three versions and whether I'll be able to keep three version up to date -
> esp. given that I don't have much automation for this.

Personally, I don't think it makes sense to commit to maintaining there
separate versions.  It seems like a really big committment.

-- 
Ricardo


  parent reply	other threads:[~2024-03-01 22:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 16:36 Contribute or create a channel? Hartmut Goebel
2024-03-01 18:16 ` Saku Laesvuori
2024-03-02 10:35   ` Hartmut Goebel
2024-03-01 21:13 ` Attila Lendvai
2024-03-01 22:35   ` Ricardo Wurmus
2024-03-12 13:18     ` Attila Lendvai
2024-03-12 16:56       ` Troy Figiel
2024-03-12 22:43       ` Carlo Zancanaro
2024-03-13 12:35         ` Attila Lendvai
2024-03-14 18:06           ` Josselin Poiret
2024-03-01 22:39 ` Ricardo Wurmus [this message]
2024-03-02 10:32   ` Hartmut Goebel
2024-03-04  8:32     ` Andreas Enge
2024-03-05 14:19       ` Hartmut Goebel
2024-03-05 22:34         ` Ricardo Wurmus

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=87y1b1shfm.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@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 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).