Re: Workflow for releasing new upstream versions to experimental?

To: debian-med@lists.debian.org
Subject: Re: Workflow for releasing new upstream versions to experimental?
From: Andrius Merkys <merkys@debian.org>
Date: Tue, 9 Feb 2021 19:48:47 +0200
Message-id: <[🔎] 5204e6d9-4f9f-d3c1-ef8a-48bcfbfe87d1@debian.org>
In-reply-to: <[🔎] CAD=WrcLycR=WLbNYn=euQnrB5XE8O28SJu4ti68i0Ee-d4BnMQ@mail.gmail.com>
References: <[🔎] CAJN1928WefTX-HLrMgi28tPdoTwE=NSy69SeqLGHqBD7pb0QBw@mail.gmail.com> <[🔎] CAD=WrcLycR=WLbNYn=euQnrB5XE8O28SJu4ti68i0Ee-d4BnMQ@mail.gmail.com>

On 2021-02-09 19:43, Michael Crusoe wrote:
> I strongly prefer a separate branch for experimental, to avoid commit
> reverts and the like.

+1

Best,
Andrius

Reply to:

References:
- Workflow for releasing new upstream versions to experimental?
  - From: Nilesh Patra <nilesh@debian.org>
- Re: Workflow for releasing new upstream versions to experimental?
  - From: Michael Crusoe <michael.crusoe@gmail.com>

Prev by Date: Re: Workflow for releasing new upstream versions to experimental?
Next by Date: Python louvain packages naming confusion.
Previous by thread: Re: Workflow for releasing new upstream versions to experimental?
Next by thread: Python louvain packages naming confusion.
Index(es):
- Date
- Thread