> On Nov 16, 2021, at 6:05 PM, Joan Touzet <woh...@apache.org> wrote:
> 
> On 16/11/2021 17:53, Joan Touzet wrote:
>> On 16/11/2021 16:08, Nick Vatamaniuc wrote:
>>> As for voting for making these proper releases, I am not really
>>> looking forward to the SVN pushes, signing, checksumming, and
>>> collecting votes for these deps.
>> Scriptable, shouldn't be hard if someone has time.
>>> Especially for a NIF with just 2
>>> functions in it.  Wonder what can be simplified there. Can voting be
>>> done in a GH release draft comments section as opposed a dev@couchdb.
>> No, all votes must be on the mailing list, sorry.
> 
> Just to add to this we're not supposed to use the GH release system for any 
> 'official' release, and in fact Infra is in talks with GH to have that system 
> disabled for all apache/* repos. I would absolutely avoid using the GH 
> release system as a basis for the Apache artefacts, and I'd be worried that 
> your scripting today could be undermined tomorrow.
> 
> I'm not saying that's right or wrong, it's just what I've heard. If you have 
> concerns, take them up with Infra directly.
> 
> Do we really think these apps are going to have a lot of churn and need a lot 
> of releases?

I could see `erlfdb` needing a regular release cadence, but I’m willing to see 
what can be done to comply with the ASF regulations in a semi-automated way. 
The other repos we’ve been discussing are somewhat more stable, although part 
of the motivation for publishing packages is to drive more interest in them and 
that could lead to more releases.

Tangentially-related question for you: one of the CI jobs for erlfdb is using a 
container image built from this Dockerfile:

https://github.com/apache/couchdb-erlfdb/blob/main/.devcontainer/Dockerfile

Should I publish that image as a tag in apache/couchdbci-debian, even though 
it’s basically a completely different build than the other images in there? 
Creating a whole new e.g. apache/erlfdbci repo for it seems like overkill, but 
I’m curious to hear your thoughts. Would something like this work?

        apache/couchdbci-debian:erlfdb-erlang-24.1.4-fdb-6.3.18

Cheers, Adam

Reply via email to