MIME-Version: 1.0
From: Roman Shaposhnik <roman@zededa.com>
Date: Sun, 27 Jun 2021 19:03:01 -0700
Message-ID: <CAMmSBy9tDCt6rWvMkzenaGQXrLOP+q9s7xJyfwFRojhfE0mzvw@mail.gmail.com>
Subject: Plan for RISCV64 in Alpine 3.15
To: ~alpine/devel@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"

Hi!

so first of all -- thank you all for taking RISCV forward
while I was traveling -- much appreciated! I see that
we now have a builder that produces packages and they
are actually getting deposited at the usual places. E.g.:
    https://dl-cdn.alpinelinux.org/alpine/edge/main/riscv64/

Given that, here's my first few infrastructure related questions:
  1. what does it take for edge packages to show up on:
         https://pkgs.alpinelinux.org/packages ?
  2. in general, do we produce the final consumable aritfacts
      for the Edge builds? Things like:
             https://alpinelinux.org/downloads/

With that out of the way, personally, I'm going to spend this
coming week making sure that:
    * bootstrap.sh is back to functional
    * we get to produce at least the following artifacts:
          * MINI ROOT FILESYSTEM
          * VIRTUAL
    * see if we can get rid of !tests on builders and selectively
      disable tests in those packages that just need it.

Personally, I also have two SBCs I will be testing Alpine on.

Now, the last question I have is this: what would be the criteria
for the # of packages or anything else to officially release RISCV64
as part of Alpine 3.15?

Thanks,
Roman.